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"?
recc_attr: FATTR4_OWNER (36)
fattr4_owner: nobody
length: 6
contents: nobody
fill bytes: opaque data
recc_attr: FATTR4_OWNER_GROUP (37)
fattr4_owner_group: nwra@xxxxxxxxxxxxx
length: 18
contents: nwra@xxxxxxxxxxxxx
fill bytes: opaque data
- Don't log if the username is "nobody"? Although since this is independently
configurable on the different machines this seems like a bad idea. Maybe don't
log if there is no domain part at all?
This is on EL6 with nfs-utils-1.2.3-15.el6_2.1
Orion Poplawski
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
