I just created a symbolic link for one of my users so he can ftp files into a directory outside of his account (above the docroot). The problem is that the link works for me as root however he cannot access that link as it gives him a "550: no such file or directory" error. Ownership for the link are set up for his username.

Do I need to adjust any other permissions to get it working?

Thanks.

Even if you have permissions for the symbolic link, I believe you will need permissions to the actual directory that will allow him to upload to that directory. I would probably give it group write permissions and stick his username in the group for that directory (or make a new one).

Ben

Just thought I'd follow up...

I contacted my host (Rackspace) and they attempted to get it to work however it seems that I cannot give a user "ftponly" access as well as limiting that user to a specific directory through the symlink. Basically, if I allow the symlink, he can view directories that I don't want him to. Leaving "ftponly" ownership in place will block directories that I don't want the user to go to but also blocks the symlink. So it looks like I'm stuck.

I'm still open to suggestions if anyone has any.

Thanks.

heh typical rackspace text book answer. you can set the users shell to /sbin/nologin which will restrict him to ftp only. You can do what you want to do you just have to play around with the permissions and ownership.

I set the account to /bin/false which doesn't allow him to to telnet in. And set ownership on his account to "ftponly" which limits him accordingly. Do you have any suggestions for setting the ownership and permissions while keeping him as an ftp/no telnet account?

Thanks