From: Steve Dickson <steved@redhat.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: [PATCH 0/3] Enable the setting of a kernel module parameter from nfs.conf
Date: Wed, 14 Apr 2021 14:10:37 -0400 [thread overview]
Message-ID: <20210414181040.7108-1-steved@redhat.com> (raw)
This is a tweak of the patch set Alice Mitchell posted last July [1].
It enables the setting of the nfs4_unique_id kernel module
parameter from /etc/nfs.conf.
Things I tweaked:
* Introduce a new [kernel] section in nfs.conf which only
contains the nfs4_unique_id setting... For now...
* nfs4_unique_id can be set to two different values
- nfs4_unique_id = ${machine-id} will use /etc/machine-id
as the unique id.
- nfs4_unique_id = ${hostname} will use the system's hostname
as the unique id.
* The new nfs-config systemd service need to be enabled for the
/etc/modprobe.d/nfs.conf file to be created with
the "options nfs nfs4_unique_id=" set.
I see this patch set is not a way to set the nfs4_unique_id
module parameter... I see it as a beginning of a way to set
all module parameters from /etc/nfs.conf, which I think
is a good thing...
[1] https://www.spinics.net/lists/linux-nfs/msg78658.html
Alice Mitchell (3):
nfs-utils: Enable the retrieval of raw config settings without
expansion
nfs-utils: Add support for further ${variable} expansions in nfs.conf
nfs-utils: Update nfs4_unique_id module parameter from the nfs.conf
value
configure.ac | 1 +
nfs.conf | 4 +-
support/include/conffile.h | 1 +
support/nfs/conffile.c | 283 ++++++++++++++++++++++++++++++++--
systemd/Makefile.am | 3 +
systemd/nfs-client.target | 3 +
systemd/nfs-conf-export.sh | 28 ++++
systemd/nfs-config.service.in | 18 +++
systemd/nfs.conf.man | 19 ++-
tools/nfsconf/nfsconf.man | 10 +-
tools/nfsconf/nfsconfcli.c | 22 ++-
11 files changed, 372 insertions(+), 20 deletions(-)
create mode 100755 systemd/nfs-conf-export.sh
create mode 100644 systemd/nfs-config.service.in
--
2.30.2
next reply other threads:[~2021-04-14 18:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 18:10 Steve Dickson [this message]
2021-04-14 18:10 ` [PATCH 1/3] nfs-utils: Enable the retrieval of raw config settings without expansion Steve Dickson
2021-05-06 17:29 ` Steve Dickson
2021-04-14 18:10 ` [PATCH 2/3] nfs-utils: Add support for further ${variable} expansions in nfs.conf Steve Dickson
2021-04-14 18:10 ` [PATCH 3/3] nfs-utils: Update nfs4_unique_id module parameter from the nfs.conf value Steve Dickson
2021-04-14 23:26 ` [PATCH 0/3] Enable the setting of a kernel module parameter from nfs.conf Chuck Lever III
2021-04-15 15:33 ` Steve Dickson
2021-04-15 16:37 ` Chuck Lever III
2021-04-15 23:30 ` Trond Myklebust
2021-04-16 0:40 ` Trond Myklebust
2021-04-17 16:33 ` Steve Dickson
2021-04-17 18:09 ` Trond Myklebust
2021-04-17 16:18 ` Steve Dickson
2021-04-17 16:36 ` Chuck Lever III
2021-04-17 17:50 ` Steve Dickson
2021-04-18 16:51 ` Chuck Lever III
2021-04-20 13:11 ` Steve Dickson
2021-04-20 14:09 ` Chuck Lever III
2021-04-20 14:31 ` Trond Myklebust
2021-04-20 17:18 ` J. Bruce Fields
2021-04-20 17:28 ` Trond Myklebust
2021-04-20 17:40 ` bfields
2021-04-20 17:53 ` Trond Myklebust
2021-04-20 18:16 ` bfields
2021-04-20 19:30 ` Steve Dickson
2021-04-20 18:47 ` Steve Dickson
2021-04-20 18:26 ` Steve Dickson
2021-05-13 0:29 ` NeilBrown
2021-05-18 12:38 ` Steve Dickson
2021-05-21 2:39 ` NeilBrown
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=20210414181040.7108-1-steved@redhat.com \
--to=steved@redhat.com \
--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