summaryrefslogtreecommitdiffstats
path: root/utils/gssd/gssd.c
diff options
context:
space:
mode:
authorChuck Lever <chuck.lever@oracle.com>2013-03-23 08:08:36 -0400
committerSteve Dickson <steved@redhat.com>2013-03-25 10:09:10 -0400
commit6888d305d8683d178239170794ce8debdaaaacd8 (patch)
tree78f804ea13ca4b55b5f1af9fd356ef32b30249c6 /utils/gssd/gssd.c
parente661019a2827aa0b303f4b2be54f0670c68812bf (diff)
downloadnfs-utils-6888d305d8683d178239170794ce8debdaaaacd8.tar.gz
nfs-utils-6888d305d8683d178239170794ce8debdaaaacd8.tar.xz
nfs-utils-6888d305d8683d178239170794ce8debdaaaacd8.zip
gssd: Clarify use of the term "machine credentials" in rpc.gssd(8)
Our NFSv4 implementation uses machine credentials for operations that manage state on behalf of the whole client (for example, SETCLIENTID or RENEW). The rpc.gssd man page is missing a description of this usage, especially in the discussion of the "-n" option. The issue is that rpc.gssd's "-n" option requires root to acquire a user credential. In the absense of a system keytab (for instance, if the system is diskless) root's credential is not to be used as the machine credential that manages NFSv4 state. Group the discussion of machine credentials and UID 0 in one place to help clarify the discussion and simplify the description of several of these options. Acked-by: J. Bruce Fields <bfields@fieldses.org> Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Signed-off-by: Steve Dickson <steved@redhat.com>
Diffstat (limited to 'utils/gssd/gssd.c')
0 files changed, 0 insertions, 0 deletions