From: Martin Pitt <martin.pitt@ubuntu.com>
To: linux-nfs@vger.kernel.org
Cc: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] [PATCH 2/2] systemd: Relax dependencies of services
Date: Tue, 3 Mar 2015 21:12:14 +0100 [thread overview]
Message-ID: <20150303201214.GA3473@piware.de> (raw)
In-Reply-To: <20150303180809.GJ3058@in.waw.pl>
Hello all,
Zbigniew Jędrzejewski-Szmek [2015-03-03 19:08 +0100]:
> Are you sure that all of those nfs daemons do not require
> sockets.target and other stuff provided by basic.target to be ready?
The corresponding upstart jobs trigger on virtual file systems (/sys,
etc.) and rpcbind, and we've used them for years. Also, NFS does not
yet use socket activation, or talks to other services on sockets
(except for rpcbind), so we don't need sockets.target either. The
other dependencies (some network.target, some nss-lookup.target, etc.)
are already specified explicitly. So I'm quite sure.
That said, there's of course always a nonzero chance that this breaks
in a case which I haven't tested. In particular, I didn't test
kerberos/gssd, I'd appreciate if someone who has a real-world setup
with that could give this a spin.
Thanks,
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
next prev parent reply other threads:[~2015-03-03 20:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 17:28 [PATCH 0/2] some systemd unit changes Martin Pitt
2015-03-03 17:28 ` [PATCH 1/2] systemd: Order NFS server before client Martin Pitt
2015-03-03 17:58 ` [systemd-devel] " Zbigniew Jędrzejewski-Szmek
2015-03-03 17:28 ` [PATCH 2/2] systemd: Relax dependencies of services Martin Pitt
2015-03-03 18:08 ` [systemd-devel] " Zbigniew Jędrzejewski-Szmek
2015-03-03 20:12 ` Martin Pitt [this message]
2015-03-03 21:44 ` Steve Dickson
2015-03-19 18:20 ` [systemd-devel] [PATCH 0/2] some systemd unit changes Steve Dickson
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=20150303201214.GA3473@piware.de \
--to=martin.pitt@ubuntu.com \
--cc=linux-nfs@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).