Package: corosync Version: 1.0.0-2 Severity: serious Tags: patch User: initscripts-ng-de...@lists.alioth.debian.org Usertags: incorrect-dependency
With dependency based boot sequencing, I discovered what I believe is a bug in the init.d scripts of this package. The scripts uses files in /usr/ and should depend on $remote_fs. Btw, as the script start a daemon, it should not really start in rcS.d/, but instead start in runlevels 2-5, to get switching to and from runlevel 1 working properly. This will require more changes than this patch provides. This patch should solve the dependency issue. Setting severity to serious, the script will start to early during boot. diff -ur ../corosync-1.0.0/debian/corosync.init ../corosync-1.0.0-pere/debian/corosync.init --- ../corosync-1.0.0/debian/corosync.init 2009-10-04 15:19:37.000000000 +0200 +++ ../corosync-1.0.0-pere/debian/corosync.init 2009-10-04 15:20:38.000000000 +0200 @@ -2,10 +2,8 @@ # ### BEGIN INIT INFO # Provides: corosync -# Required-Start: $network -# Required-Stop: $network -# Should-Start: -# Should-Stop: +# Required-Start: $network $remote_fs +# Required-Stop: $network $remote_fs # Default-Start: S # Default-Stop: 0 1 6 # Short-Description: corosync cluster framework Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
