Package: smartmontools Version: 5.38~cvs20071118-2 Severity: important Tags: patch User: [EMAIL PROTECTED] Usertags: incorrect-dependency
I just checked the shutdown order in unstable on a machine with smartmontools and dependency based boot sequencing enabled, and discovered that the smartmontools script was inserted into the wrong location for runlevels 0 and 6. It should depend on $remote_fs, to make sure it is stopped before sendsigs kills all processes, and to make sure /usr/ is mounted before it try to use programs in /usr/bin/. Here is a patch to solve it. diff -ur smartmontools-5.38~rc0.orig/debian/smartmontools.init smartmontools-5.38~rc0/debian/smartmontools.init --- smartmontools-5.38~rc0.orig/debian/smartmontools.init 2008-03-04 22:28:03.000000000 +0100 +++ smartmontools-5.38~rc0/debian/smartmontools.init 2008-03-04 22:28:43.000000000 +0100 @@ -9,8 +9,8 @@ # ### BEGIN INIT INFO # Provides: smartmontools -# Required-Start: $syslog $local_fs -# Required-Stop: $syslog $local_fs +# Required-Start: $syslog $remote_fs +# Required-Stop: $syslog $remote_fs # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: SMART monitoring daemon As the stop script do not seem to do much except killing the daemon, that task might be better left to the sendsigs script in runlevel 0 and 6, to speed up shutdown. 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]
