[Splashy-devel] Re: Bug#400598: splashy: RUNLEVEL not defined

[Tim Dijkstra]

Op Sat, 2 Dec 2006 01:12:17 -0500
schreef Luis <lemsx1 at gmail.com>:

> Otavio,
> 
> I found other bugs in splashy-update-progress-steps. This patch fixes
> those bugs as well. Please disregard the patch I sent before for that
> file (see Bug # 400598 on DBTS).
> 
> To avoid possible confusions, I added the full file as well. This is
> assume to be used with Splashy 0.2.1.
> 
> The idea is that simply listing the files in /etc/rcS.d and
> /etc/rc2.d/[KS]* gives you symlinks that are not actually pointing to
> files and scripts that do not all log_end_msg at all. This new patch
> only cares about files calling log_end_msg for our progressbar.

Hmm, my idea of taking also the other scripts into account was that
those do matter for the startup time. I mean, if we a few scripts in 
S01, S02, S03 that call log_end_msg then tons that do not, we would
hit 100% already in S03, while there is still lots of stuff to do.

> The bug is triggered when you have scripts at the end of the resulting
> step file that do not call log_end_msg. Leaving the progressbar in,
> say, 94% and never completing to 100%, therefore, Splashy just sits
> there waiting until it times out!

I thought splashy got a signal to stop by [kgx]dm or something?


Well, I haven't looked at the code for a while. I was really busy
finishing my thesis. The good news is, that it is just approved, so I
can do some splashy develpement again.

grts Tim