[systemd-devel] Special targets - should they Want or be WantedBy?
mk.fraggod at gmail.com
Thu Mar 17 22:31:11 PDT 2011
On Fri, 18 Mar 2011 00:34:19 +0100
Lennart Poettering <lennart at poettering.net> wrote:
> But what about the other direction? We definitely want network.target in
> the boot transaction if NM or network.service is part of it too. Because
> only then the network consuming services can be synchronized
> properly. Hence we want those two services pull in network.target, as a
> signal "Hey, we implement this, and when it is up, you can use it".
> So, here's what I am going to do now:
> a) Modify the Description= strings of the various target units where
> this applies to make clear that they exist for SysV/LSB compat only.
> b) Remove dbus.target
> c) Add a Wants+Before to syslog.socket on syslog.target. Since the
> socket is already enough to make logging possible this is all that is
> d) fix the systemd code which parses LSB headers to interpret Provides
> like this.
> e) patch NM upstream and NTP in F15 to add the necessary dependencies.
> And Andrey, thanks a lot for pointing us to this problem and the
> Questions? Anything we didn't think about?
That'd make all the systems with currently enabled services in
network.target.wants misconfigured - network should fail on these
unless something Requires= (or Wants=) network.target explicitly (which
was marked as a wrong way to depend on network), so I think maybe some
larger announcement for packagers is in order as well, to leave less
broken systems and angry users as a result ;)
Mike Kazantsev // fraggod.net
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: not available
More information about the systemd-devel