Package: dumputils Version: 1.0.1-1 Severity: important Tags: patch User: [EMAIL PROTECTED] Usertags: incorrect-dependency
When testing dependency based boot sequencing, I discovered a bug in the init.d script for dumputils. The start and stop dependencies are not correct. The script list the wrong start and stop runlevels, and do not depend on $remote_fs needed for /usr/ to be guaranteed to be mounted. Also, there is a typo using &named instead of the correct $named dependency. The current script is missing the required required-stop header, which should be present to avoid confusing the tools used to enable dependency based boot sequencing. Fixing these issues is a release goal for lenny, so it is good if it is fixed quickly. This patch solve the issue: diff -ur dumputils-1.1.1.orig/etc.init.d.dumputils dumputils-1.1.1/etc.init.d.dumputils --- dumputils-1.1.1.orig/etc.init.d.dumputils 2007-08-21 15:59:18.000000000 +0200 +++ dumputils-1.1.1/etc.init.d.dumputils 2008-02-17 16:52:54.000000000 +0100 @@ -3,9 +3,10 @@ # ### BEGIN INIT INFO # Provides: dumputils -# Required-Start: $network &named -# Default-Start: 2 3 4 5 -# Default-Stop: 0 1 6 +# Required-Start: $remote_fs $network $named +# Required-Stop: +# Default-Start: S +# Default-Stop: # Short-Description: Initializes the Linux Kernel Crash Dump system # Description: Provides user space applications to control the # LKCD modules and manage the 2 stage dump process. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
