Petter Reinholdtsen wrote: [hmm, your Bcc: shows up when I press reply-all, thats interesting...] > [Török Edwin] > >> $ sudo update-bootsystem-insserv >> > > Thank you for testing the dependency based boot system, and reporting > this problem. > >
Your welcome, I am running with insserv's boot system since ... a long time, and didn't encounter any serious problems. At least the system is able to boot and shutdown properly ... faster than with the default boot ordering ;) Petter Reinholdtsen wrote: > Gah, the brain is receiving something the eyes didn't send. :/ > > This is in fact bug #458346 in util-linux, tagged pending. Still, it > is a bug in the init.d script headers. > > > Yes, I've noticed, and wrote a follow-up mail to close this bug, since I considered it to be a duplicate of that bug. >> I can work around this by using 'BAD_INSSERV_HACKER=true >> Actually I can work it around by editing hwclockfirst.sh as described in #458346. >> dpkg-reconfigure insserv' as described on the wiki, but IMHO >> update-bootsystem-insserv should be able to handle this situation. >> > > What kind of situation are you talking about? Insserv not capable of > covering up bugs in the LSB headers in the init.d scripts? > I've seen hwclock.sh and hwclockfirst.sh in your /etc/rcS.d (in the message you posted to initscripts-ng-devel), and I thought it must be something wrong on my system that caused those 2 scripts to not be handled by insserv. I was wrong, its just a bug in hwclock's initscripts, and not in insserv. >> the error about the loop is probably due to #458582] >> > > Actually, the loop is real, between mysql-ndb-mgm and mysql. Both > depend on each other, and there is no ordering possible for installing > these scripts while fulfilling their dependencies. > > mysql depend on (Required-Start) mysql-ndb-mgm, and mysql-ndb-mgm > depend on (Required-Stop) on mysql. One of these need to be reduced > to a optional dependency for this to be reduced to the problem > documented in bug #458582. The mysql dependency bug should probably > be reported seperately to mysql. > > Happy hacking, > I don't have a good understanding of Required-Start and Required-Stop, but my interpretation was: * Required-Start means: when _current service_ has to be started, we need to start these before * Required-Stop means: when any of these are stopped, we also need to stop _current service_ * Thus Required-Start and Required-Stop dependencies are independt, and don't influence each other. when starting mysql: depends on mysql-ndb-mgm, syslog; mysql-ndb-mgm depends on syslog: start syslog, mysql-ndb-mgm, mysql, no loops when stopping mysql: listed in mysql-ndb-mgm's required-stop: stop that first and then mysql: stop mysql-ndb-mgm, mysql, syslog, no loops Am I wrong, and does it really mean: When we need to stop _current service_, everything in Required-Stop needs to be stopped ? I've read http://wiki.debian.org/LSBInitScripts, and its still not very clear why mysql and mysql-ndb-mgm are in a dep. loop. Thanks, Edwin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
