From: Scott Mayhew <smayhew@redhat.com>
To: steved@redhat.com
Cc: jlayton@kernel.org, yoyang@redhat.com, linux-nfs@vger.kernel.org
Subject: [nfs-utils PATCH v2 0/2] nfsdctl version handling fixes
Date: Fri, 10 Jan 2025 15:17:44 -0500 [thread overview]
Message-ID: <20250110201746.869995-1-smayhew@redhat.com> (raw)
Two changes in how nfsdctl does version handling. The first patch makes
the 'nfsdctl version' command behave according to the man page for w.r.t
handling +4/-4, e.g.
# utils/nfsdctl/nfsdctl
nfsdctl> threads 0
nfsdctl> version
+3.0 +4.0 +4.1 +4.2
nfsdctl> version -4
nfsdctl> version
+3.0 -4.0 -4.1 -4.2
nfsdctl> version +4
nfsdctl> version
+3.0 +4.0 +4.1 +4.2
nfsdctl> version -4 +4.2
nfsdctl> version
+3.0 -4.0 -4.1 +4.2
nfsdctl> ^D
The second patch makes nfsdctl's handling of the nfsd version options in
nfs.conf behave like rpc.nfsd's. This is important since the systemd
service file will fall back to rpc.nfsd if nfsdctl fails. I'll send a
test script and test results in a followup email.
-Scott
Scott Mayhew (2):
nfsdctl: tweak the version subcommand behavior
nfsdctl: tweak the nfs.conf version handling
utils/nfsdctl/nfsdctl.c | 69 +++++++++++++++++++++++++++++++++++------
1 file changed, 59 insertions(+), 10 deletions(-)
--
2.45.2
next reply other threads:[~2025-01-10 20:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 20:17 Scott Mayhew [this message]
2025-01-10 20:17 ` [nfs-utils PATCH v2 1/2] nfsdctl: tweak the version subcommand behavior Scott Mayhew
2025-01-10 20:17 ` [nfs-utils PATCH v2 2/2] nfsdctl: tweak the nfs.conf version handling Scott Mayhew
2025-01-10 20:26 ` [nfs-utils PATCH v2 0/2] nfsdctl version handling fixes Scott Mayhew
2025-01-11 12:30 ` Jeff Layton
2025-01-13 23:11 ` Scott Mayhew
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=20250110201746.869995-1-smayhew@redhat.com \
--to=smayhew@redhat.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
--cc=yoyang@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