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.
NFS assumes a model that UIDs/GIDs are consistent across platforms. Therefore, you need proper permissions on remote files systems to control local access permissions. There is an exception made for UID 0, which allows mapping it to a non-privileged user.
Thanks for the reply. I agree that the settings need to be done on the NFS server side.
But this share will be mounted on this host by ROOT always.
Had we required to give access to specific users to mount this share then I know it can be set on NFS share. But once its mounted, can the access list be modified in such way that only specific users get access to this share after mount?
Post mount usermod 770 command or chown command does not work on the mount point.
The mount point does not control permissions below that point in the directory tree. There are no inheritable permissions, short of ACLs (which are implementation dependent).
Once mounted, the existing remote file and directory permissions are in control. You can root_squash or all_squash, but that just maps UID 0, or all UIDs to the anonymous UID.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.