The nfs-config service translates distro-specific startup configuration into "environment" variable read and used by systemd unit files. Currently it is only run once, so subsequent changes to the distro-specific files do not take effect when an nfs service is restarted. If we change "RemainAfterExit=yes" to "RemainAfterExit=no" then the service will be restarted before any dependant service is started, so the environment file will always be up to date. Reported-and-tested-by: Benjamin Coddington <bcodding@xxxxxxxxxx> Signed-off-by: NeilBrown <neilb@xxxxxxxx> --- systemd/nfs-config.service | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/systemd/nfs-config.service b/systemd/nfs-config.service index 7f653058f424..e0a7f83314f5 100644 --- a/systemd/nfs-config.service +++ b/systemd/nfs-config.service @@ -5,5 +5,9 @@ DefaultDependencies=no [Service] Type=oneshot -RemainAfterExit=yes +# This service needs to run any time any nfs service +# is started, so changes to local config files get +# incorporated. Having "RemainAfterExit=no" (the default) +# ensures this happens. +RemainAfterExit=no ExecStart=/usr/lib/systemd/scripts/nfs-utils_env.sh -- 2.7.2
Attachment:
signature.asc
Description: PGP signature
