create a user in a second HD
- Thread starter winger
- Start date
floyd
Verified User
- Joined
- Mar 29, 2005
- Messages
- 6,255
You keep using that word after I have told you I don't know what it means. I feel I am being insulted but I am not sure.
I or the community have nothing to gain by continuing with this.
nobaloney
NoBaloney Internet Svcs - In Memoriam †
@floyd:
According to man tar on both Redhat/CentOS and Debian/Ubunut distributions (I just checked) you can use the -h or --dereference options to treat symlinks by following them and archiving/restoring them as if they were real.
The program I remember as not following symlinks is apache, but it depends on an option in the configuration. You can not follow symlinks, follow them, or only follow them if the owner matches. Lots of Google hits here.
Everyone:
Exim delivers email based on where it is. /home just happens to be where it is when using Dovecot on DirectAdmin. That part of the code that's hard-coded was written by DirectAdmin staff. I've just found a reference in my current RC (and maybe in all exim.conf files in use by DirectAdmin; I haven't checked), to $home, in the userforward director.
So it may very well work. However recently I believe someone has posted on these forums that the forwards in the .forward file weren't working. Are they? If they are, then $home can possibly be substituted for /home in the local_delivery director.
However I'm not sure what exactly $home contains at the point where it needs to be checked.
Documentation is here (exim.org). Anyone have time to check it?
Jeff
According to man tar on both Redhat/CentOS and Debian/Ubunut distributions (I just checked) you can use the -h or --dereference options to treat symlinks by following them and archiving/restoring them as if they were real.
The program I remember as not following symlinks is apache, but it depends on an option in the configuration. You can not follow symlinks, follow them, or only follow them if the owner matches. Lots of Google hits here.
Everyone:
Exim delivers email based on where it is. /home just happens to be where it is when using Dovecot on DirectAdmin. That part of the code that's hard-coded was written by DirectAdmin staff. I've just found a reference in my current RC (and maybe in all exim.conf files in use by DirectAdmin; I haven't checked), to $home, in the userforward director.
So it may very well work. However recently I believe someone has posted on these forums that the forwards in the .forward file weren't working. Are they? If they are, then $home can possibly be substituted for /home in the local_delivery director.
However I'm not sure what exactly $home contains at the point where it needs to be checked.
Documentation is here (exim.org). Anyone have time to check it?
Jeff
I have some users that was moved to a second hard drive mounted as home2
mail works and everythign is great except ftp. I cannot add or modify ftp users it says :
Cannot Execute Your Request
Details
That is not a valid path. Either it is not in your home directory, it doesn't exist, it contains symbolic links, or it contains invalid characters
Any Ideas?????????
mail works and everythign is great except ftp. I cannot add or modify ftp users it says :
Cannot Execute Your Request
Details
That is not a valid path. Either it is not in your home directory, it doesn't exist, it contains symbolic links, or it contains invalid characters
Any Ideas?????????
- Joined
- Feb 27, 2003
- Messages
- 8,469
Hello,
That error message is generated when DA checks the ftp path for custom accounts. It's looking for a few things (which can generate that message).
1) Check /etc/passwd for the system account. Make sure the home path is /home2/username, if the user is under /home2.
2) There also cannot be any symbolic links in the path. No directories can be present in any part of the path.
3) the path must exist, and be chowned to the User. (root won't be allowed)
4) it must be a valid path (obviously).. must start with the / character, and end with the name of the directory it's pointed to.
5) The path must be below the home directory of the User, so similar to check #1, the path would need to be something like /home2/user/path, or /home2/user/some/other/path, etc...
On a side note (not related to the ftp issue), regarding quotas and 2nd drives:
http://www.directadmin.com/features.php?id=611
John
That error message is generated when DA checks the ftp path for custom accounts. It's looking for a few things (which can generate that message).
1) Check /etc/passwd for the system account. Make sure the home path is /home2/username, if the user is under /home2.
2) There also cannot be any symbolic links in the path. No directories can be present in any part of the path.
3) the path must exist, and be chowned to the User. (root won't be allowed)
4) it must be a valid path (obviously).. must start with the / character, and end with the name of the directory it's pointed to.
5) The path must be below the home directory of the User, so similar to check #1, the path would need to be something like /home2/user/path, or /home2/user/some/other/path, etc...
On a side note (not related to the ftp issue), regarding quotas and 2nd drives:
http://www.directadmin.com/features.php?id=611
John
nobaloney
NoBaloney Internet Svcs - In Memoriam †
If I recall correctly, you just change DirectAdmin to use /home2, and it will create new users in /home2 but users created earlier won't be affected. And when /home2 is full, do the same, moving to /home3.
Jeff
Jeff