From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: [~amd64] NFS server broken again :(
Date: Fri, 31 Oct 2014 14:27:43 -0400 [thread overview]
Message-ID: <CAGfcS_nBN41FvfAXarnYoaZ8GhcpWROqkYiW9U4A-ZHU6e_m2Q@mail.gmail.com> (raw)
In-Reply-To: <CAOdo=SyLmZdGXGy3EgpkdSBe8AzxCkED34=wK4kKuBg6Qvh0uw@mail.gmail.com>
On Fri, Oct 31, 2014 at 1:34 PM, Tom H <tomh0665@gmail.com> wrote:
> Is "After" really necessary as an option? I've never come across a
> service that uses "After" without a "Requires" or a Wants" but I've
> never taken the time to look.
>
Hmm, I found After more common that Wants, but maybe I only look at
units that have problems. :)
I think the intent is to handle optional dependencies, but in practice
I don't know that it works well. It would almost be better to have
some kind of cluster config file that specifies all the actual
dependencies (possibly including cross-host) and have it spit out all
the unit dependencies automatically. That is a bit much to ask for
now, and probably a bit much for somebody who just wants their laptop
to launch kde after all their mounts are ready.
Specifying After vs Wants separately does make sense. Dependency
doesn't have to imply sequential.
--
Rich
next prev parent reply other threads:[~2014-10-31 18:27 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
2014-10-31 17:34 ` Tom H
2014-10-31 18:27 ` Rich Freeman [this message]
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_nBN41FvfAXarnYoaZ8GhcpWROqkYiW9U4A-ZHU6e_m2Q@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