Linux NFS development
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Scott Mayhew <smayhew@redhat.com>, linux-nfs@vger.kernel.org
Subject: Re: [nfs-utils PATCH] rpc.idmapd: Add a reference to nfsidmap(8) on the man page
Date: Fri, 23 Jan 2015 10:31:26 -0500	[thread overview]
Message-ID: <54C2694E.6020108@RedHat.com> (raw)
In-Reply-To: <1419371092-18037-1-git-send-email-smayhew@redhat.com>



On 12/23/2014 04:44 PM, Scott Mayhew wrote:
> Even though the 'new' idmapper used by the client has been around for
> several years, a lot of users seem to be unaware of its existence.
> 
> Signed-off-by: Scott Mayhew <smayhew@redhat.com>
Committed...

steved.

> ---
>  utils/idmapd/idmapd.man | 13 ++++++++++++-
>  1 file changed, 12 insertions(+), 1 deletion(-)
> 
> diff --git a/utils/idmapd/idmapd.man b/utils/idmapd/idmapd.man
> index 185cd1b..c809f78 100644
> --- a/utils/idmapd/idmapd.man
> +++ b/utils/idmapd/idmapd.man
> @@ -20,6 +20,16 @@ is the NFSv4 ID <-> name mapping daemon.  It provides functionality to
>  the NFSv4 kernel client and server, to which it communicates via
>  upcalls, by translating user and group IDs to names, and vice versa.
>  .Pp
> +Note that on more recent kernels only the NFSv4 server uses
> +.Nm .
> +The NFSv4 client instead uses
> +.Xr nfsidmap 8 ,
> +and only falls back to 
> +.Nm 
> +if there was a problem running the
> +.Xr nfsidmap 8
> +program.
> +.Pp
>  The options are as follows:
>  .Bl -tag -width Ds_imagedir
>  .It Fl v
> @@ -58,7 +68,8 @@ messages to console, and with a verbosity level of 3.
>  .Sh FILES
>  .Pa /etc/idmapd.conf
>  .Sh SEE ALSO
> -.Xr idmapd.conf 5
> +.Xr idmapd.conf 5 ,
> +.Xr nfsidmap 8
>  .\".Sh SEE ALSO
>  .\".Xr nylon.conf 4
>  .\" .Sh COMPATIBILITY
> 

      reply	other threads:[~2015-01-23 15:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-23 21:44 [nfs-utils PATCH] rpc.idmapd: Add a reference to nfsidmap(8) on the man page Scott Mayhew
2015-01-23 15:31 ` Steve Dickson [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=54C2694E.6020108@RedHat.com \
    --to=steved@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=smayhew@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox