From: Doug Nazar <nazard@nazar.ca>
To: Steve Dickson <SteveD@RedHat.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"J. Bruce Fields" <bfields@fieldses.org>
Subject: Re: nfs-utils README updates
Date: Fri, 17 Jul 2020 18:15:39 -0400 [thread overview]
Message-ID: <8ef6b702-0cca-e5c7-d873-afc21effe4df@nazar.ca> (raw)
In-Reply-To: <0555b3d1-8cbe-c3d8-2214-2bf7d3d65286@RedHat.com>
On 2020-07-17 13:34, Steve Dickson wrote:
> 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.
Sure, although I don't use systemd myself, I'll have to trust it's correct.
> What script did you have to add 'auth_rpcgss' to?
> It should be automatically be loaded when the sunrpc
> module is loaded.
/etc/init.d/rpc.svcgssd (on Gentoo).
Looking into it, looks like sunrpc is included & loaded from the
initramfs that Gentoo's 'genkernel' creates (for root nfs setups) but
not the auth_rpcgss or rpcsec_gss_krb5 modules. Which makes some sense,
since i can't think of an easy way to do a krb5 root fs with a generic
initramfs. Kind of a chicken-egg issue with getting kerberos initialized.
I suppose the other option is to allow svcgssd to startup and wait for
that file to appear. I already have patches that convert it to use
libevent so that shouldn't be too much work to add.
Doug
prev parent reply other threads:[~2020-07-17 22:15 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
2020-07-17 20:29 ` J. Bruce Fields
2020-07-17 22:15 ` Doug Nazar [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=8ef6b702-0cca-e5c7-d873-afc21effe4df@nazar.ca \
--to=nazard@nazar.ca \
--cc=SteveD@RedHat.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
/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).