summaryrefslogtreecommitdiff
path: root/systemd
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2022-11-21 14:24:00 -0500
committerSteve Dickson <steved@redhat.com>2022-11-21 14:24:00 -0500
commit580ac005d11ddb9a9622e380ba8e947ad743a38f (patch)
treeadb7a62ec49210cfefcd365afbc4bdc7e4cda595 /systemd
parent46a114733ad67ca8ada5a42bb48b88379e9346db (diff)
downloadnfs-utils-580ac005d11ddb9a9622e380ba8e947ad743a38f.tar.gz
nfsd: allow server scope to be set with config or command line.nfs-utils-2-6-3-rc4
NFSv4.1 and later require the server to report a "scope". Servers with the same scope are expected to understand each other's state ids etc, though may not accept them - this ensure there can be no misunderstanding. This is helpful for migration. Servers with different scope are known to be different and if a server appears to change scope on a restart, lock recovery must not be attempted. It is important for fail-over configurations to have the same scope for all server instances. Linux NFSD sets scope to host name. It is common for fail-over configurations to use different host names on different server nodes. So the default is not good for these configurations and must be over-ridden. As discussed in https://github.com/ClusterLabs/resource-agents/issues/1644 some HA management tools attempt to address this with calls to "unshare" and "hostname" before running "rpc.nfsd". This is unnecessarily cumbersome. This patch adds a "-S" command-line option and nfsd.scope config value so that the scope can be set easily for nfsd. Signed-off-by: NeilBrown <neilb@suse.de> Signed-off-by: Steve Dickson <steved@redhat.com>
Diffstat (limited to 'systemd')
-rw-r--r--systemd/nfs.conf.man1
1 files changed, 1 insertions, 0 deletions
diff --git a/systemd/nfs.conf.man b/systemd/nfs.conf.man
index b95c05a..bfd3380 100644
--- a/systemd/nfs.conf.man
+++ b/systemd/nfs.conf.man
@@ -172,6 +172,7 @@ for details.
Recognized values:
.BR threads ,
.BR host ,
+.BR scope ,
.BR port ,
.BR grace-time ,
.BR lease-time ,