[Juha Heinanen] > hope this info is enough to reproduce and fix the problem.
It is. I believe I see the problem. These two form a loop: > addscript mysql <<'EOF' > ### BEGIN INIT INFO > # Provides: mysql > # Required-Start: $remote_fs $syslog > # Required-Stop: $remote_fs $syslog > # Should-Start: $network $named $time > # Should-Stop: $network $named $time > # Default-Start: 2 3 4 5 > # Default-Stop: 0 1 6 > # Short-Description: Start and stop the mysql database server daemon > # Description: Controls the main MySQL database server daemon "mysqld" > # and its wrapper script "mysqld_safe". > ### END INIT INFO > EOF > addscript pdns <<'EOF' > ### BEGIN INIT INFO > # Provides: pdns > # Required-Start: $network $remote_fs $syslog > # Required-Stop: $network $remote_fs $syslog > # Default-Start: 2 3 4 5 > # Default-Stop: 0 1 6 > # Should-Start: slapd mysql postgresql > # Should-Stop: slapd mysql postgresql > # Short-Description: PDNS is a versatile high performance authoritative > nameserver. > ### END INIT INFO > EOF pdns provides $named and want to start after mysql, while mysql want to start after $named. This leads to this dependency loop: mysql -> $named -> pdns -> mysql -> $named. No idea how to best fix it. pdns can't run both before and after mysql. Either pdns need to drop the mysql relationship, or mysql need to drop the $named relationship. The latter might be the best option, but I leave it to the pdns and mysql maintainers to discuss how to best order these init.d scripts. This error has exposed a bug in my archive wide consistency check. It currently ignores the insserv.conf.d/ entries, which need to be taken into account to discover this bug. 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
