Package:  uniconfd
Version:  4.4.1-0.1
Severity: important
Tags:     patch
User:     [EMAIL PROTECTED]
Usertags: incorrect-dependency

I just checked the shutdown order in unstable on a machine with
dependency based boot sequencing enabled, and discovered a problem
with the init.d scripts provided in uniconfd.  It stops to late and
start to early, as it do not depend on $remote_fs which guarantee that
/usr/ will be mounted and that it stops before sendsigs.

Another issue is that the init.d script list S in its stop runlevel
list.  This make a useless stop symlink in rcS.d/.  It should not be
included.

Here is a patch to solve these issues.

diff -ur wvstreams-4.4.1/debian/uniconfd.init 
wvstreams-4.4.1.new/debian/uniconfd.init
--- wvstreams-4.4.1/debian/uniconfd.init        2007-07-19 23:22:30.000000000 
+0200
+++ wvstreams-4.4.1.new/debian/uniconfd.init    2008-03-08 23:48:49.000000000 
+0100
@@ -2,12 +2,10 @@
 #
 ### BEGIN INIT INFO
 # Provides:          uniconfd
-# Required-Start:    $local_fs
-# Required-Stop:     $local_fs
-# Should-Start:      $local_fs
-# Should-Stop:       $local_fs
+# Required-Start:    $remote_fs
+# Required-Stop:     $remote_fs
 # Default-Start:     2 3 4 5
-# Default-Stop:      S 0 1 6
+# Default-Stop:      0 1 6
 # Short-Description: Server that manages UniConf elements
 # Description:       A server that accepts incoming TCP or Unix
 #                    connections, and gets or sets UniConf elements

Happy hacking,
--
Petter Reinholdtsen



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

Reply via email to