diff options
| author | NeilBrown <neilb@suse.com> | 2018-12-05 13:52:37 -0500 |
|---|---|---|
| committer | Steve Dickson <steved@redhat.com> | 2018-12-10 13:38:35 -0500 |
| commit | bb5fd8f2d6c7e75f2bb23ff55daf43cf3089bb45 (patch) | |
| tree | 036a690d1676c1bc9775bdcb4deb7c5baf3b9210 /systemd/rpc-statd.service | |
| parent | 4090cc55b7ecc8ef1cfdc5b46f8151ad4a96166a (diff) | |
| download | nfs-utils-bb5fd8f2d6c7e75f2bb23ff55daf43cf3089bb45.tar.gz | |
systemd: run statd-notify even when nfs-client isn't enabled
When NFS filesytems are mounted, nfs-client.target really should
be enabled. However it is possible to mount NFS filesystems
without this (providing gss isn't used) and it mostly works.
One aspect that doesn't work is that sm-notify isn't run, so the server
isn't told to drop any locks from the previous client instance.
This can result in confusing failures: if a client crashes while
holding a lock, it won't be able to get the same lock after a reboot.
While this isn't a complete solution (nfs-client really should be
enabled), adding a dependency from rpc-statd to rpc-statd-notify is
easy, has no down sides, and could help avoid confusion.
Signed-off-by: NeilBrown <neilb@suse.com>
Signed-off-by: Steve Dickson <steved@redhat.com>
Diffstat (limited to 'systemd/rpc-statd.service')
| -rw-r--r-- | systemd/rpc-statd.service | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/systemd/rpc-statd.service b/systemd/rpc-statd.service index 1f4e6a8..3e92cf7 100644 --- a/systemd/rpc-statd.service +++ b/systemd/rpc-statd.service @@ -4,6 +4,7 @@ DefaultDependencies=no Conflicts=umount.target Requires=nss-lookup.target rpcbind.socket Wants=network-online.target +Wants=rpc-statd-notify.service After=network-online.target nss-lookup.target rpcbind.socket PartOf=nfs-utils.service |