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

[Kel Modderman]

On Tuesday 23 September 2008 06:05:32 Luca Capello wrote:
> Hi Kel!
> 
> On Sun, 21 Sep 2008 16:38:41 +0200, Kel Modderman wrote:
> > To fix splashy and have it inserted in dependency based boot as expected simply
> > remove the $all keyword from Required-Stop. On my system it will start splashy
> > in runlevel S just after mountkernfs and before udev, and stop first in
> > sequence of runlevels 0 and 6.
> 
> This seems to not be the case on a clean sid-amd64 chroot (and the same
> happens on my *real* sid-amd64):
> =====
> root at gismo:/# ls -1 /etc/rcS.d/
> [...]
> S03mountkernfs.sh
> S04udev
> S05mountdevsubfs.sh
> S06bootlogd
> S06hwclock.sh
> S06hwclockfirst.sh
> S06splashy
> [...]
> root at gismo:/#
> =====

In addition to removing $all from Required-Stop, try adding:
X-Start-Before: mountdevsubfs udev

> 
> At reboot/shutdown, splashy must be the *first* script to be started,
> which is not the case again on the above clean sid-amd64 chroot:
> =====
> root at gismo:/# ls -1 /etc/rc0.d/
> K01hwclock.sh
> K01sendsigs
> K01splashy
> [...]
> root at gismo:/#
> =====

What is wrong if those scripts execute in parallel ?

Thanks, Kel.