Re: [PATCH 0/1] details for starting nfs-idmapd also on clients

[Steve Langasek <steve.langasek@ubuntu.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 --]