From: DENIEL Philippe <philippe.deniel@cea.fr>
To: linux-nfs@vger.kernel.org
Subject: NFSv4 : question on the resolution of unknown users and groups
Date: Mon, 28 Mar 2011 14:40:17 +0200 [thread overview]
Message-ID: <4D9081B1.1020205@cea.fr> (raw)
Hi,
I am in the following situation : a file belonging to the user whose
(uid, gid) is (15678,15678) is to be exported via NFS through a client
and / or a server than knows nothing about this user (there is no entry
in /etc/passwd, in the yellow pages or whatever is used to maintain
users's maps).
When using NFSv3, I see this on the client:
# ls -ld unknown/
drwxr-xr-x 2 15678 15678 4096 Mar 28 11:15 unknown/
When using NFSv4 (the rpc.idmapd is running on both client and server
and is configured homogeneously) I see this:
# ls -ld unknown/
drwxr-xr-x 2 nobody nobody 4096 Mar 28 11:15 unknown/
With wireshark I can see that the server itself replies the string
"nobody" as OWNER and OWNER_GROUP. I guess the libnfslibmap (used inside
the rpc.idmapd) is not resolving (15678, 15678) and returns an error,
making the nfsd returning nobody. The nfs-utils-lib that I use is
1.1.5-1 (it's a F13 machine).
Is what I saw a regular behaviour ? How shoud I configure the client
and/or the server to have the same display in NFSv4 and NFSv3 when
querying attributes on objects belonging to an unknown user ?
Regards
Philippe
reply other threads:[~2011-03-28 13:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4D9081B1.1020205@cea.fr \
--to=philippe.deniel@cea.fr \
--cc=linux-nfs@vger.kernel.org \
/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).