On Wed, 2002-06-12 at 09:01, Ruffus, William (W.L.) wrote: > > My linux client client can't properly deal with files with uid or gid > 60001 on a non-linux NFS server ( Solaris 5.8 or HPUX 11 so far). ... > > Files with uid or gid 60001 (nobody) on the NFS server are listed as > uid or gid as number 4292967294 in "ls -l" or "ls -ln" . ... > "stat filename" reports the uid as "-2" .
My own search pulled up this very quickly: http://www.mcsr.olemiss.edu/cgi-bin/man-cgi?passwd+4 Excerpt: UID CONVENTIONS UID -2 NFS 'nobody'. Note that because uid_t is unsigned, -2 is mapped to the special value 60001 by NFS. I would guess what you're seeing is non-conventional NFS servers on Solaris and HPUX. NFS (according to the above) is supposed to use an unsigned UID, but for some reason those servers are sending out a "negative" number. When the Linux client interperets that as an unsigned UID, it ends up with the value 4292967294. If you see on the server that the UID is 60001, then those servers are probably using some HACK to map the reserved UID 60001 to some other value for their own clients. The fix, then, would be to not use reserved UID's for your users. Change the UID of any user currently mapped to 60001 or 60002 to some other value, and then fix all of their files: find / -user 60001 -print | xargs chown <user>:<group> _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
