On a VM that boots very fast and with out kerberos
enabled a systemd ordering cycle happens between
nfs-client and nfs-server units when both were
enabled.
Having nfs-client start the gssd daemons in the
same matter as the nfs-server does ('After=') seemed
to eliminated the ordering cycle.
Signed-off-by: Steve Dickson <steved@xxxxxxxxxx>
---
systemd/nfs-client.target | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/systemd/nfs-client.target b/systemd/nfs-client.target
index 474f5e9..87a1ce8 100644
--- a/systemd/nfs-client.target
+++ b/systemd/nfs-client.target
@@ -7,7 +7,7 @@ Wants=remote-fs-pre.target
# start that on demand if needed.
Wants=rpc-gssd.service rpc-svcgssd.service auth-rpcgss-module.service
Wants=nfs-blkmap.service rpc-statd-notify.service
-Before=rpc-gssd.service rpc-svcgssd.service nfs-blkmap.service
+After=rpc-gssd.service rpc-svcgssd.service nfs-blkmap.service
[Install]
WantedBy=multi-user.target
--
1.9.3
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
