From: Steve Dickson <SteveD@RedHat.com>
To: Doug Nazar <nazard@nazar.ca>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: nfs-utils README updates
Date: Fri, 17 Jul 2020 13:34:03 -0400 [thread overview]
Message-ID: <0555b3d1-8cbe-c3d8-2214-2bf7d3d65286@RedHat.com> (raw)
In-Reply-To: <34f07da7-250d-f354-bf59-74b9f1a0e16f@nazar.ca>
Hey Doug,
On 7/16/20 5:36 PM, Doug Nazar wrote:
> I was looking through the README to ensure my systems followed the correct setup and noticed a few things.
>
> Looks like the reference to libnfsidmap can be dropped.
>
> It looks like nfsdcld is again the correct setup for client tracking. A section should be added to SERVER STARTUP to include nfsdcld on NFS4+ servers.
>
> Should it mention which modules are required before starting? I've had to locally add 'auth_rpcgss' to my startup scripts or svcgssd will bail on startup.
>
> Any other changes or best practices that should be mentioned before I send a patch?
Yes... the README is dreadfully out of date... although most of it has
not changed but a lot has... esp when it comes to the systemd set up..
although the systemd/README is pretty accurate... Maybe a point to
the systemd/README in the top README would be good.
What script did you have to add 'auth_rpcgss' to?
It should be automatically be loaded when the sunrpc
module is loaded.
Thanks for taking a look!
steved.
next prev parent reply other threads:[~2020-07-17 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 21:36 nfs-utils README updates Doug Nazar
2020-07-17 17:34 ` Steve Dickson [this message]
2020-07-17 20:29 ` J. Bruce Fields
2020-07-17 22:15 ` Doug Nazar
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=0555b3d1-8cbe-c3d8-2214-2bf7d3d65286@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=nazard@nazar.ca \
/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;
as well as URLs for NNTP newsgroup(s).