[systemd-devel] Breaking ordering cycles... a suggestion.

[Michael Biebl]

2012/5/17 Kay Sievers <kay at vrfy.org>:
> On Thu, May 17, 2012 at 4:02 PM, Colin Guthrie <gmane at colin.guthr.ie> wrote:
>> I know this has been discussed a lot but it's still showing up for me on
>> occasion, especially with 3rd party non-LSB init scripts.
>>
>> My suggestion would be to prioritise the jobs that we delete... can we
>> tell that a job relates to a unit? And if so can we tell if a unit is
>> sysv, lsb or native? If so I'd propose that when a job needs ot be
>> deleted, we try to find a sysv job first, then an lsb then a native.
>> That way we shouldn't end up with a sucky 3rd party sysv script killing
>> prefdm startup as seems to be happening here:
>> https://bugs.mageia.org/show_bug.cgi?id=5262#c36
>>
>> Would that be feasible?
>
> Having some sort of context to be able to prioritize things makes
> probably sense.
>
> We've seen cases where some exotic storage daemon kicked out the D-Bus
> unit from the transaction.

We've seen this quite often on Debian, too, due to sysv init scripts
doing "interesting" stuff, like being both started in rcS.d and rc2.d.

Would be great if we somehow could mark dbus.service as essential so
it is never kicked out.
Dropping dbus.service (or dbus.socket) breaks your system badly.