From: Steve Langasek <steve.langasek@ubuntu.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: Martin Pitt <martin.pitt@ubuntu.com>,
linux-nfs@vger.kernel.org, systemd-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/1] details for starting nfs-idmapd also on clients
Date: Fri, 6 Mar 2015 10:20:31 -0800 [thread overview]
Message-ID: <20150306182031.GA6228@virgil.dodds.net> (raw)
In-Reply-To: <54F9DA9D.8010106@RedHat.com>
[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]
On Fri, Mar 06, 2015 at 11:49:33AM -0500, Steve Dickson wrote:
> On 03/06/2015 06:15 AM, Martin Pitt wrote:
> > Hello all,
> > Steve Langasek pointed out in [1] that idmapd is also necessary on the client
> > side. It isn't for my very simple NFSv4 test, but then again I don't know that
> > much about the various other modes of operation.
> > This patch starts nfs-idmapd.service on clients too.
> This is distro specific... Other distros use the
> key ring based nfsidmap(5) command to do the id mapping.
> Make note, with new kernels the default upcall is to the
> nfsdimap command, if that fails then the rpc.idmapd daemon
> is tried. Meaning there are two upcalls for every id map
> when rpc.idmapd is used. This was the reason for the switch.
Ah, thanks for the feedback. We do have nfsidmapd enabled, I had overlooked
that rpc.idmapd was no longer being used on the client. We'll stick with
just using nfsidmap then.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slangasek@ubuntu.com vorlon@debian.org
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-03-06 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 11:15 [PATCH 0/1] details for starting nfs-idmapd also on clients Martin Pitt
2015-03-06 11:15 ` [PATCH] systemd: start " Martin Pitt
2015-03-06 16:49 ` [PATCH 0/1] details for starting " Steve Dickson
2015-03-06 18:20 ` Steve Langasek [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=20150306182031.GA6228@virgil.dodds.net \
--to=steve.langasek@ubuntu.com \
--cc=SteveD@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=martin.pitt@ubuntu.com \
--cc=systemd-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.