Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux

NFS: Update idmapper documentation

Signed-off-by: Bryan Schumaker <bjschuma@netapp.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

authored by

Bryan Schumaker and committed by
Trond Myklebust
a602bea3 3cd0f37a

+14 -6
+14 -6
Documentation/filesystems/nfs/idmapper.txt
··· 4 4 ========= 5 5 Id mapper is used by NFS to translate user and group ids into names, and to 6 6 translate user and group names into ids. Part of this translation involves 7 - performing an upcall to userspace to request the information. Id mapper will 8 - user request-key to perform this upcall and cache the result. The program 9 - /usr/sbin/nfs.idmap should be called by request-key, and will perform the 10 - translation and initialize a key with the resulting information. 7 + performing an upcall to userspace to request the information. There are two 8 + ways NFS could obtain this information: placing a call to /sbin/request-key 9 + or by placing a call to the rpc.idmap daemon. 11 10 12 - NFS_USE_NEW_IDMAPPER must be selected when configuring the kernel to use this 13 - feature. 11 + NFS will attempt to call /sbin/request-key first. If this succeeds, the 12 + result will be cached using the generic request-key cache. This call should 13 + only fail if /etc/request-key.conf is not configured for the id_resolver key 14 + type, see the "Configuring" section below if you wish to use the request-key 15 + method. 16 + 17 + If the call to /sbin/request-key fails (if /etc/request-key.conf is not 18 + configured with the id_resolver key type), then the idmapper will ask the 19 + legacy rpc.idmap daemon for the id mapping. This result will be stored 20 + in a custom NFS idmap cache. 21 + 14 22 15 23 =========== 16 24 Configuring