Your message dated Sun, 25 May 2008 21:48:12 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: usplash init stop target rework
has caused the Debian Bug report #482015,
regarding usplash: should use omitpit feature to avoid getting killed by
sendsigs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
482015: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482015
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: usplash
Version: 0.5.19-1
In version 2.86.ds1-57 of sysvinit, I removed the special handling of
splash screen processes from init.d/sendsigs. The splash screen
handlers are expected to use the omitpid feature of init.d/sendsigs to
avoid getting killed at the wrong time during shutdown. Adding
something like this when starting usplash should solve it:
mkdir -p /lib/init/rw/sendsigs.omit.d
rm -f /lib/init/rw/sendsigs.omit.d/usplash
ln -s /var/run/usplash.pid /lib/init/rw/sendsigs.omit.d/usplash
Happy hacking,
--
Petter Reinholdtsen
--- End Message ---
--- Begin Message ---
uploaded usplash urgently before doing a cool bike tour,
so doing the bug closures by hand. thanks Petter Reinholdtsen
--
maks
ps the changes below fix aboves bugs
usplash (0.5.19-2) unstable; urgency=low
.
[ Petter Reinholdtsen ]
* usplash: should use omitpit feature to avoid getting killed by
sendsigs
* usplash: starts too late in the shutdown sequence
--- End Message ---
