adding 2nd thread to domain - sym link error

C

Chrysalis

Verified User
Joined
Aug 25, 2004
Messages
1,321
Location
uk
I added a 2nd domain to a user and it came up with unable to make symlink error, but still added the domain.

My guess is it couldnt point public_html to the dir because it already is used for 1st domain.

Is this a bug that happens to everyone?

Can the error be stopped by not trying to make the symlink since 1st domain exists or making public_html2 or something?

thanks
 
I don't know of anyway to turn the symlink feature off. Can you run the ln command and create the public_html link to the new domain properly, or does that also give you errors?
 
I dont need to try the command as I know it will fail, the problem is the public_html link already exists pointing to the first domain and I am led to believe when adding a 2nd domain it tries to make a new public_html --> domain link of which it cant do since public_html already points to 1st domain.
 
What Operating System are you running?

It's working fine for me on FreeBSD 4.10 and probably should on any Operating system since the link command is the same as far as I know.
 
Ok then I am probably wrong on this, perhaps I should have tried it a second time before I posted :)

os is FreeBSD5.3
 
Why would you add a second thread if there's already one covering the error?

Jeff
 
Hi I ran a search and couldnt find another thread with the same problem.

Now I tried the same thing again on a different server and it produced no errors, but as I know it is impossible to have 1 dir link to 2 domains I decided to login to the shell and check.

The main domain for the sake of this discussion I will call domain.com, and the second domain I added is hello.com.

ls -l output in user's home dir.

drwx--x--x 4 freshxxxx freshxxxx 512 Feb 1 04:49 domains
drwx------ 2 freshxxxx freshxxxx 512 Feb 1 04:49 mail
-rw-r--r-- 1 freshxxxx freshxxxx 4767203 Jan 26 06:40 modernbill-demo-zend[1].tar.gz
lrwxr-xr-x 1 freshxxxx freshxxxx 31 Feb 1 04:49 public_html -> ./domains/hello.com/public_html

As you can see the original symlink is gone if the user added a 2nd domain to a production website the next time he logged into ftp and entered the publiv_html dir he would be awefully confused as he would be in his new empty dir.

Domains subdir has both domains and both domains have the public_html dir's so I expect no problem with the website functioning but the problem is with the symlink I think DA handles this badly and 2nd domain should have been public_html2 -> ./domains/hello.com/public_html.
 
You must log in or register to reply here.
Back
Top