[Pkg-sysvinit-devel] Upstart support for LSB headers (Two line init.d scripts? Sure, that will work!)

Thomas Goirand zigo at debian.org
Thu Feb 6 13:36:51 UTC 2014

On 02/06/2014 07:06 PM, Petter Reinholdtsen wrote:
>> Since last summer, OpenRC has full support for LSB headers. Also, I
>> believe that OpenRC is the only init system replacement which allows
>> to mix dependencies with LSB or it's own implementation.
> That is not the case.  Both systemd and upstart allow this as well.

I knew that both systemd and upstart can use LSB header scripts. But I
read that upstart (at least) would launch these only at the end of the
boot process, not mixing them in the boot order with upstart jobs. Can
any Upstart specialist (Steve maybe?) can tell if this is right or
wrong? What is systemd doing exactly with the LSB dependencies?

With OpenRC, what happens is that the LSB headers are transformed into
the internal syntax of OpenRC (eg: use, need, after, provide, etc.),
which makes it possible to have LSB header scripts be integrated within
the ordering calculation, just as if they were native OpenRC runscripts.
They are also involved in the dependency loop breaking system that has
recently been added to OpenRC.

BTW, Debian has a way too many LSB header scripts with Required-Start:
$all, which is very bad. A decent init system has to deal with this, and
there's no sane way to do so but arbitrarily breaking what the author of
the script wrote. A lintian warning telling that $all is just bad would
be a very nice thing. How does systemd & upstart deal with this pile of
garbage that Required-Start: $all is?



More information about the Pkg-sysvinit-devel mailing list