On Thu, Jan 1, 2009 at 11:23, Petter Reinholdtsen <p...@hungry.com> wrote:
> [Gordon Farquharson] > I am not talking about insserv optimization. I am talking about > sysv-rc (/etc/init.d/rc) optimizations, ie the normal debian boot > system. Ok, I misunderstood before. > Neither the normal sysv-rc boot system nor insserv have this > capability. There is no way to know if some other script will insert > itself before or after a given script in any system. It is always > possible for a script to insert itself before or after another script. Ok, strictly you are correct :-) But with sysv-rc, you can at least get close to the desired result by setting the script number. I suspect that the 'z' in zleds is not there by accident (zleds is an upstream script in the nslu2-utils package). > Btw, why run a script both at the end of rcS.d and at the start of > rc[0-6].d? It seem redundant to me. I'm looking into why it was done like that, to see how to make it work in another way. > Why not only run one at the end > of rcS.d (which is imedately before the start of rc[0-6].d), and then > again at the end of rc[0-6].d? This is a key point: what do I set in the LSB header to ensure that the script is run at the _end_ of each of these runlevels? > What should happen when runlevel is > switched from 2 to 3, btw? Should the leds change or not? No. The LEDs remain the same for run levels 2-5. > The main feature of insserv is correctness, not speed. It make sure Ok, thanks for clarifying that for me. The references on the web about insserv often link insserv with reducing the boot time, which lead me to this incorrect assumption. Thanks for your patience with me. 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
