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

[Luca Capello]

Hi Petter!

On Tue, 23 Sep 2008 14:17:50 +0200, Petter Reinholdtsen wrote:
> [Luca Capello]
>> I really don't understand what's the problem here: splashy asks to
>> be started after mountkernfs.sh, which means that without any other
>> directive should be placed at S04.  And this is not the case.
>
> I do not understand.  The example you include show splashy started
> with S04 and after mountkernfs.  What is the problem?

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.

1) splashy must start and stop ASAP, otherwise messages are shown on the
   screen (and if this is the case I don't see why I'd install splashy).
   And splashy must start alone, not in parallel (again for the previous
   point in parenthesis).

2) insserv acts differently WRT the different directives I put in the
   splashy init script, which is quite strange: firstly I've S04udev,
   S06procps and S25splashy and then S04splashy, S04procps and S05udev.

Unfortunately, I know splashy is a corner case, something very similar
to bootchart [3].

Thx, bye,
Gismo / Luca

Footnotes: 
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=yes&bug=485307#101
[2] without any modification procps is at S06
[3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491391
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 314 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/splashy-devel/attachments/20080923/55267f0c/attachment.pgp