[Splashy-devel] Bug#485307: Bug#485307: splashy starts too late during startup/shutdown

[Petter Reinholdtsen]

[Luca Capello]
> No, the latest example I posted [1] shows splashy started at S04 but
> *after* other stuff, in that specific case procps [2].
> 
> Either I haven't understood how splashy works or insserv's
> dependency calculation is in some way random.

Right.  I believe I see where the confusion is.  The scripts with the
same sequence number do not have any inter-dependencies, and can be
started in parallell.  This mean, any ordering of scripts with the
same sequence number is according to the dependency information.
Scripts with the same sequence number can be seen as unordered.  If
you want a specific ordering for scripts, some dependency need to be
documented to specify that ordering.  When enabling concurrent
booting, all scripts with the same sequence number are started in
parallell.  :)

Have a look at the dependency graph for your system to get some feel
on which scripts can be started in parallell.  It can be done like
this:

  /usr/share/insserv/check-initd-order -g > start.dot
  dotty start.dot

Happy hacking,
-- 
Petter Reinholdtsen