Re: Spurious rpc.idmapd nss_getpwnam: name 'nobody' does not map into domain messages

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2012-06-01 at 15:53 +0000, Orion Poplawski wrote:
> I'm seeing a fair number of these messages on our file server:
> 
> Jun  1 09:37:58 alexandria rpc.idmapd[28890]: nss_getpwnam: name 'nobody' does
> not map into domain 'cora.nwra.com'
> 
> I think they are coming from accessing files on another file server that are
> owned by an unknown uid (user left and was removed from the user database). 
> These files end up owned by "nobody" (as expected) on the remote system:
> 
> drwxr-xr-x.  7 nobody nwra 4096 Mar 15  2010 analysis_data
> 
> Now, this seems like a perfectly normal operation and so shouldn't generate a
> system log message.  First two possible fixes I can think of:
> 
> - Should the remote system send the username as "nobody@xxxxxxxxxxxxx" instead
> of just "nobody"?

No. According to section 5.8 of RFC3530, it should use the name "nobody"
without a domain, and the idmapper should be mapping that string to the
anonymous user (i.e. uid -2).

-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@xxxxxxxxxx
www.netapp.com

��.n��������+%������w��{.n�����{��w���jg��������ݢj����G�������j:+v���w�m������w�������h�����٥



[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux