From: Jim Rees <rees@umich.edu>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Orion Poplawski <orion@cora.nwra.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: Spurious rpc.idmapd nss_getpwnam: name 'nobody' does not map into domain messages
Date: Fri, 1 Jun 2012 13:10:12 -0400 [thread overview]
Message-ID: <20120601171012.GA9054@umich.edu> (raw)
In-Reply-To: <1338568876.2774.25.camel@lade.trondhjem.org>
Myklebust, Trond wrote:
> Well, it's mapping it to "nobody" id 99:
Yes, that's the correct thing to do if a user "nobody" exists.
Is it? RFC3530 says "nobody" (on the wire) is the anonymous user. If the
server has a real user whose local name is "nobody," should the nfs
anonymous user be mapped to the real local user named "nobody", or should it
be mapped to uid -2?
I'm inclined to say that if you have a real user named "nobody" on linux
then you get what you deserve.
prev parent reply other threads:[~2012-06-01 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 15:53 Spurious rpc.idmapd nss_getpwnam: name 'nobody' does not map into domain messages Orion Poplawski
2012-06-01 15:58 ` Myklebust, Trond
2012-06-01 16:26 ` Orion Poplawski
2012-06-01 16:41 ` Myklebust, Trond
2012-06-01 16:53 ` Orion Poplawski
2012-06-01 17:10 ` Jim Rees [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120601171012.GA9054@umich.edu \
--to=rees@umich.edu \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=orion@cora.nwra.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).