Anthony Messina wrote:
why does nfsnobody have such a long uid/gid number in a fresh install?
# grep nfsnobody /etc/passwd nfsnobody:x:4294967294:4294967294:Anonymous NFS User:/var/lib/nfs:/sbin/nologin
this has caused problems on previous nfs4 installations. i usually have to change it to 65534 to get things to work.
Cameron Simpson wrote:
That's the 32-bit version of "-2". 65534 is the 16 bit version. It probably tracks the "uid_t" type size.
Anthony Messina replied:
thank you for your reply. trouble is, when i use that number, i get the following message in my logs:
rpc.idmapd[2086]: nfsdcb: id '-2' too big!
and the idmapping fails to work properly. in order to use that 32 bit number, is there something else i might not be configuring properly?
What are you attempting to talk to?
Unix and Unix-like systems used to use 16 bit user numbers because no-one expected a Unix box to have more than 60 000 users.
Unfortunately, with centralised authentication schemes and large organisations, that assumption became false: it did become theoretically possible that any one of 100 000 users might log into a Unix computer. So user IDs (and group IDs) were extended to 32 bits. Having a nfsnobody user in the middle of umpteen-thousand normal user IDs was considered confusing, so it was moved.
There are still some operating systems around that haven't changed (often due to compatibility concerns).
In your case, either you'll have to limit Fedora to 60 000 users and use 65534 as the nfsnobody userID, or you'll have to reconfigure the "other" computer(s) to use 32 bit userIDs.
Hope this helps,
James.