hi there, i've looked at the link you send me... and something caught my eye:
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.
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.
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.
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?
thanks for your tip!