Package:  acpid
Version:  1.0.4-7
Tags:     patch
User:     [EMAIL PROTECTED]
Usertags: incorrect-dependency

When testing dependency based boot sequencing, I discovered what I
believe is a bug in the init.d/acpid script.  It need a mounted /usr/,
but do not depend on $remote_fs which is the dependency required for
scripts needing /usr/.  Also, based on the commends in the script, I
believe it should start before hal, and *dm, and stop after them, so I
added optional reverse dependencies for this.

This patch should solve the issue.

diff -ur acpid-1.0.6.orig/debian/acpid.init.d acpid-1.0.6/debian/acpid.init.d
--- acpid-1.0.6.orig/debian/acpid.init.d        2008-01-06 22:05:13.000000000 
+0100
+++ acpid-1.0.6/debian/acpid.init.d     2008-01-06 22:41:43.000000000 +0100
@@ -1,10 +1,10 @@
 #! /bin/sh -e
 ### BEGIN INIT INFO
 # Provides:          acpid
-# Required-Start:    $syslog
-# Required-Stop:     $syslog
-# Should-Start:      $local_fs
-# Should-Stop:       $local_fs
+# Required-Start:    $remote_fs $syslog
+# Required-Stop:     $remote_fs $syslog
+# X-Start-Before:    kdm gdm xdm hal
+# X-Stop-After:      kdm gdm xdm hal
 # Default-Start:     2 3 4 5
 # Default-Stop:      0 1 6
 # Short-Description: Start the Advanced Configuration and Power Interface 
daemon

As the stop script do not seem to do anything except killing the
daemon, that task might be better left to the sendsigs script in
runlevel 0 and 6.  If this is indeed the case, I recommend removing 0
and 6 from the Default-Stop list.

Happy hacking,
--
Petter Reinholdtsen



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

Reply via email to