Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
i've been playing with NFS, and I realised that if I just mount the server folder, that folder permissioning will be of what is specified in the server.
E.g. if the folder is created on the server by UID 500 (user1), when I mount on the client, the permission will belong to UID 500.
But client's UID 500 could be someone else. How can I manipulate that?
hi there, i've looked at the link you send me... and something caught my eye:
Code:
map_identity
This option tells the server to assume that the client uses the same uids and gids as the server. This option is on by default.
map_daemon
This option tells the NFS server to assume that client and server do not share the same uid/gid space. rpc.nfsd then builds a list that maps IDs between client and server by querying the client's rpc.ugidd daemon.
map_static
This option allows you to specify the name of a file that contains a static map of uids and gids. For example, map_static=/etc/nfs/vlight.map would specify the /etc/nfs/vlight.map file as a uid/gid map. The syntax of the map file is described in the exports(5) manual page.
map_nis
This option causes the NIS server to do the uid and gid mapping.
map_daemon seems to suggest that I can use NFS and not base the permission on UID/GID only?
Also, it seems that map_static means I can create a file to specify the mapping...
are these 2 related... or separately used?
So if I don't have NIS service within my network, the only way out is to manually ensure all uid/gid are consistent throughout the network? Unless the above works?
i've never done uid mapping there, but i guess the first way, the server asks to the client "what uid does user bob have on your system?" and then converts the files with local uid for bob to be the rmeote one over that specific connection...
again these are going to ways to get around exisiting problems. if the problem is eradicated, you'll not have any work to do in the first place.
automating? autonfs can possibly cover this, but i'm not really sure what you mean.
NIS is generally being replaced by LDAP in new installations. centralized ldap user authentication would solve a huge amount of problems you don't even know exists yet...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.