Package: uruk Version: 20071101-1 Severity: minor Tags: patch User: initscripts-ng-de...@lists.alioth.debian.org Usertags: incorrect-runlevels
With dependency based boot sequencing, I discovered what I believe is a bug in the init.d script. The list of runlevels in the init.d header do not match the arguments used by update-rc.d. This was also discovered by piuparts, see its log <URL: http://piuparts.debian.org/sid/pass/uruk_20080330-1.log > which report the following: update-rc.d: warning: uruk start runlevel arguments (S) do not match LSB Default-Start values (2 3 5) <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 for new installations. For existing installations, more code is needed in the postinst. diff -ru uruk-20080330/init/uruk.in uruk-20080330-pere/init/uruk.in --- uruk-20080330/init/uruk.in 2007-11-01 07:12:19.000000000 +0100 +++ uruk-20080330-pere/init/uruk.in 2010-05-14 20:40:39.000000000 +0200 @@ -13,7 +13,7 @@ # Provides: uruk # Required-Start: $network # Required-Stop: $network -# Default-Start: 2 3 5 +# Default-Start: S # Default-Stop: 0 6 # Description: Starts uruk firewall configuration # short-description: uruk firewall configuration Do the script really need to run when single user mode is enabled? If not, it might be better to start from runlevels 1-5 instead of in rcS.d/. 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
