systemd: start nfs-idmapd also on clients

Commit Message

Martin Pitt March 6, 2015, 11:15 a.m. UTC

idmapd is needed on clients too, so start it from nfs-client.target and stop
binding to it in nfs-server.service.

https://launchpad.net/bugs/1428961
---
 systemd/nfs-client.target  | 4 ++--
 systemd/nfs-idmapd.service | 2 --
 2 files changed, 2 insertions(+), 4 deletions(-)

Patch

diff --git a/systemd/nfs-client.target b/systemd/nfs-client.target
index 9b792a3..b12d830 100644
--- a/systemd/nfs-client.target
+++ b/systemd/nfs-client.target
@@ -5,8 +5,8 @@  Wants=remote-fs-pre.target
 
 # Note: we don't "Wants=rpc-statd.service" as "mount.nfs" will arrange to
 # start that on demand if needed.
-Wants=nfs-blkmap.service rpc-statd-notify.service
-After=nfs-blkmap.service
+Wants=nfs-blkmap.service rpc-statd-notify.service nfs-idmapd.service
+After=nfs-blkmap.service nfs-idmapd.service
 
 # GSS services dependencies and ordering
 Wants=auth-rpcgss-module.service
diff --git a/systemd/nfs-idmapd.service b/systemd/nfs-idmapd.service
index df3dd9d..90d3731 100644
--- a/systemd/nfs-idmapd.service
+++ b/systemd/nfs-idmapd.service
@@ -4,8 +4,6 @@  DefaultDependencies=no
 Requires=var-lib-nfs-rpc_pipefs.mount
 After=var-lib-nfs-rpc_pipefs.mount local-fs.target
 
-BindsTo=nfs-server.service
-
 Wants=nfs-config.service
 After=nfs-config.service