From: Martin Pitt <martin.pitt@ubuntu.com>
To: linux-nfs@vger.kernel.org
Cc: Steve Langasek <steve.langasek@ubuntu.com>,
systemd-devel@lists.freedesktop.org,
Martin Pitt <martin.pitt@ubuntu.com>
Subject: [PATCH] systemd: start nfs-idmapd also on clients
Date: Fri, 6 Mar 2015 12:15:44 +0100 [thread overview]
Message-ID: <1425640544-24230-2-git-send-email-martin.pitt@ubuntu.com> (raw)
In-Reply-To: <1425640544-24230-1-git-send-email-martin.pitt@ubuntu.com>
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(-)
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
--
2.1.4
next prev parent reply other threads:[~2015-03-06 11:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 11:15 [PATCH 0/1] details for starting nfs-idmapd also on clients Martin Pitt
2015-03-06 11:15 ` Martin Pitt [this message]
2015-03-06 16:49 ` Steve Dickson
2015-03-06 18:20 ` Steve Langasek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1425640544-24230-2-git-send-email-martin.pitt@ubuntu.com \
--to=martin.pitt@ubuntu.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steve.langasek@ubuntu.com \
--cc=systemd-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.