Package:  munge
Version:  0.5.8-9
Severity: important
Tags:     patch
User:     [email protected]
Usertags: incorrect-runlevels incorrect-dependencies

With dependency based boot sequencing, I discovered what I believe is
a bug in the init.d/munge script.  The runlevel list state that it
should stop in runlevel 2.  This is inconsistent with the Debian
runlevels and the arguments used for update-rc.d.  It is also missing
dependency on $remote_fs (which is require to know that /usr/ is
mounted).  I also suspect it should be possible to install munge even
if no DNS server is installed, and because of this propose to move the
$named dependency from required to optional dependency.

<URL:http://refspecs.freestandards.org/LSB_2.1.0/LSB-generic/LSB-generic/initscrcomconv.html>
documents the LSB header format.  Some debian notes are available from
<URL:http://wiki.debian.org/LSBInitScripts>.

This patch should solve the issue.  Without it, the init.d fail to
start in runlevel 2 by default with dependency based boot sequencing,
and might start to early during boot.

diff -ru munge-0.5.8/debian/munge.init munge-0.5.8-pere/debian/munge.init
--- munge-0.5.8/debian/munge.init       2009-08-12 19:08:32.000000000 +0200
+++ munge-0.5.8-pere/debian/munge.init  2009-08-12 19:14:09.000000000 +0200
@@ -11,12 +11,12 @@
 ###############################################################################
 ### BEGIN INIT INFO
 # Provides:       munge
-# Required-Start: $named $time
-# Required-Stop:  $named $time
-# Should-Start:   $local_fs $syslog
-# Should-Stop:    $local_fs $syslog
-# Default-Start:  3 4 5
-# Default-Stop:   0 1 2 6
+# Required-Start: $remote_fs $time
+# Required-Stop:  $remote_fs $time
+# Should-Start:   $named $syslog
+# Should-Stop:    $named $syslog
+# Default-Start:  2 3 4 5
+# Default-Stop:   0 1 6
 # Short-Description:    Start/Stop the MUNGE authentication service.
 # Description:    Start/Stop the MUNGE authentication service.
 ### END INIT INFO

Happy hacking,
-- 
Petter Reinholdtsen



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to