[Luca Capello] > This is plainly wrong and has nothing to do with bootchart, since > stop-bootlogd should start *after* rmnologin, according to the LSB > headers: > ===== > (sid-amd64)[EMAIL PROTECTED]:/# grep Required-Start /etc/init.d/rmnologin > # Required-Start: $remote_fs $all > (sid-amd64)[EMAIL PROTECTED]:/# grep Required-Start > /etc/init.d/stop-bootlogd > # Required-Start: $remote_fs rmnologin > (sid-amd64)[EMAIL PROTECTED]:/# > =====
You interpret $all differently from insserv, and it is not obvious to me which interpretation is correct. The definition I am aware of for $all is: facility supported by insserv to start a script after all the other scripts, at the end of the boot sequence. The question at work is the priority of $all when there is script X depending on a script Y depending on $all. Is X part of 'all the other scripts' or not? Should $all have higher priority than other dependencies or not? At the moment, insserv consider X to be part of 'all the other scripts', and places Y after X. > This is exactly my point: it seems that insserv doesn't completely > respect the Required-Start header. It does. It just respect $all more than other dependencies. :) Patches to handle $all in a more robust way is most welcome. Because the behavoiur of $all sometimes yield unexpected results, I recommend against it use unless there is no other way to get the wanted script ordering. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
