Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 554196 - net-fs/nfs-utils: nfsclient init.d shouldn't "need" rpc.idmapd with nfsv4 idmapping request-key upcall method
Summary: net-fs/nfs-utils: nfsclient init.d shouldn't "need" rpc.idmapd with nfsv4 idm...
Status: RESOLVED DUPLICATE of bug 413173
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Network Filesystems
Depends on:
Reported: 2015-07-08 01:47 UTC by Paul B. Henson
Modified: 2015-07-13 02:51 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Paul B. Henson 2015-07-08 01:47:43 UTC
In newer kernels, if you are using the request-key method for idmapping, rpc.idmapd doesn't actually need to be running. While the /etc/idmapd.conf file is still used for configuring the nfsv4 domain, the rpc.idmapd binary is not used.

However, it always starts because it is "need"ed by the nfsclient init script.

Ideally I suppose the script could dynamically determine if it is needed by checking the kernel version and possible kernel options and the presence of the /etc/request-key.d/id_resolver.conf file, but I think it would probably be simpler to just change the "need" to a "use" and require the user to explicitly enable it if their configuration requires it.

Reproducible: Always
Comment 1 Paul B. Henson 2015-07-08 01:52:55 UTC
Hmm, I didn't think to look initially, but I see /etc/conf.d/nfsclient already has this comment:

# If you are using only nfsv3, uncomment this line:

I suppose a simple fix might be just changing that comment to "If you are using only nfsv3 or nfsv4 idmapping with the request-key upcall method".
Comment 2 SpanKY gentoo-dev 2015-07-13 02:51:42 UTC

*** This bug has been marked as a duplicate of bug 413173 ***