Hi Petter So after a lot of reading on init scripts and insserv, it seems to me that the init scripts provided by nslu2-utils are not supportable by insserv. You had written the following in a previous email thread:
--- [Gordon Farquharson] > I took the runlevel information from the nslu2-utils debian/rules: > > dh_installinit --no-start --onlyscripts --name=zleds \ > -- start 99 S 1 2 3 4 5 . stop 5 0 1 2 3 4 5 6 . This do not make sense. It is undefined what is done when there is both start and stop symlinks for the same runlevel. It should either start or stop, not both. --- and --- I believe the sysv-rc script calling the boot and shutdown scripts will not behave the way you expect if there are both start and stop symlinks for a given runlevel. I am not sure what it will do, but it is definitely not defined how it should behave. :) In short, only start or stop at a given runlevel. --- I can't find any documentation to support the assertion that one may not put the same init script in a runlevel twice (e.g. K05zleds and S99zleds in rc1.d). Actually, the Debian Policy seems to support this use: "When init changes runlevel first the targets of the links whose names start with a K are executed, each with the single argument stop, followed by the scripts prefixed with an S, each with the single argument start. (The links are those in the /etc/rcn.d directory corresponding to the new runlevel.) The K links are responsible for killing services and the S link for starting services upon entering the runlevel." The init scripts provided by nslu2-utils require exactly this functionality. I therefore provide that we add empty LSB headers to scripts in nslu2-utils to meet the release goal of having an LSB header, but document that the nslu2-utils package will not work correctly with insserv. How does this sound to everybody? Gordon -- Gordon Farquharson GnuPG Key ID: 32D6D676 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
