Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It may just be that your ftp server is set up to not follow symlinks. Or, if you are running your ftp server in a chrooted environment, /home/rmbimgs/public_html/ may not be inside the chroot.
It may just be that your ftp server is set up to not follow symlinks. Or, if you are running your ftp server in a chrooted environment, /home/rmbimgs/public_html/ may not be inside the chroot.
HTH
Forrest
since I created the symlinks via ssh as root, the symlink has a root grp and owner set. i tried changing the owner & grp to rmbsite but its not taking. any idea on how to own and grp?
It shouldn't matter who owns the symlink, if the target is available, it will just go there. The chroot command has nothing to do with ownership. What it does is basically set up an area of your hard drive for a particular use and makes it so that anything outside that area isn't able to be seen. Run 'man chroot' for more info.
You can also make /home/rmbserv/rmbimgs the real directory and /home/rmbimgs/public_html a link to that location, like
ln -s /home/rmbserv/rmbimgs /home/rmbimgs/public_html
The web server shouldn't have problem following the link by default (unless it has also been set to ignore links).
You can also make /home/rmbserv/rmbimgs the real directory and /home/rmbimgs/public_html a link to that location, like
ln -s /home/rmbserv/rmbimgs /home/rmbimgs/public_html
The web server shouldn't have problem following the link by default (unless it has also been set to ignore links).
i have another problem, i'm not able to delete any of the files on the other user. i thought by making a symblink i'd be able to control access to the files as if they were under the same web user directory.
so i guess now whats the easiest way to give myself access to the files and any new files that are added.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.