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

[Luis]

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.

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!

-- 
----)(-----
Luis Mondesi
*NIX Guru

"Feliz el hombre que ha hallado sabiduria y el hombre que consigue
discernimiento, porque el tenerla como ganancia es mejor que tener la
plata como ganancia; y el tenerla como producto, [mejor] que el oro
mismo" (Prov 3:13-14).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: splashy-update-progress-steps.diff
Type: text/x-patch
Size: 1913 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/splashy-devel/attachments/20061202/55b4fdb3/splashy-update-progress-steps.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: splashy-update-progress-steps
Type: application/octet-stream
Size: 5086 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/splashy-devel/attachments/20061202/55b4fdb3/splashy-update-progress-steps.obj