From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: [~amd64] NFS server broken again :(
Date: Tue, 28 Oct 2014 21:50:48 -0400 [thread overview]
Message-ID: <CAGfcS_mVzpTokhEVPuhp_p86DZHkr1j5rAoG1wopQiRKcWE3Sg@mail.gmail.com> (raw)
In-Reply-To: <CAOdo=SypcgJqvPAU45qOcCowEV4aF5BMKaRBuiJZDBebwwGjBA@mail.gmail.com>
On Tue, Oct 28, 2014 at 9:36 PM, Tom H <tomh0665@gmail.com> wrote:
> Since Gentoo's rpcbind.service has "Wants=rpcbind.target" and
> "Before=rpcbind.target"", having nfs-server.service depend on
> rpcbind.target rather than rpcbind.service should work as long as
> rpcbind.service is enabled.
>
> But having "Requires=rpcbind.service" and "After=rpcbind.service",
> like nfsd.service has/had, means that you don't have to enable
> rpcbind.service.
>
I was just looking at that and thinking the same thing. Nothing is
really forcing rpcbind to load the way things are specified right now.
If a service really requires another service to operate, it should say
that. There is no problem doing that via a target, but then the
target still needs to pull it in.
There seems a general tendency in systemd to express dependencies as
"after" instead of "requires." That is fine if the service doesn't
really require something else, but if there really is a true
dependency then it just causes problems when somebody doesn't notice
and fails to enable the other unit.
--
Rich
next prev parent reply other threads:[~2014-10-29 1:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 19:38 [gentoo-user] [~amd64] NFS server broken again :( walt
2014-10-27 19:56 ` Canek Peláez Valdés
2014-10-27 23:46 ` [gentoo-user] " walt
2014-10-28 1:05 ` Canek Peláez Valdés
2014-10-28 2:49 ` Tom H
2014-10-28 3:22 ` Tom H
2014-10-28 22:18 ` walt
2014-10-29 1:36 ` Tom H
2014-10-29 1:50 ` Rich Freeman [this message]
2014-10-31 17:34 ` Tom H
2014-10-31 18:27 ` Rich Freeman
2014-10-31 23:01 ` Tom H
2014-10-31 23:52 ` Rich Freeman
2014-11-03 1:37 ` Tom H
2014-11-03 3:47 ` Rich Freeman
2014-11-01 3:18 ` Jc García
2014-10-28 0:56 ` [gentoo-user] " Tom H
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=CAGfcS_mVzpTokhEVPuhp_p86DZHkr1j5rAoG1wopQiRKcWE3Sg@mail.gmail.com \
--to=rich0@gentoo.org \
--cc=gentoo-user@lists.gentoo.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