Further to this: I found that for insserv to order things correctly, a resolver facility should be available before apt-cacher-ng starts, but only if one is provided. The $named facility seems safe, as insserv.conf defines all its dependencies as optional.
Including "# Should-Start: $named" in the lsb-comments in /etc/init.d/apt-cacher-ng would fix the problem. I've successfully tested with the following in /etc/insserv/overrides/apt-cacher-ng : ### BEGIN INIT INFO # Provides: apt-cacher-ng # Required-Start: $local_fs $network $remote_fs # Required-Stop: $local_fs $network $remote_fs # Should-Start: $named # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Apt-Cacher NG package proxy # Description: This script powers up the package proxy daemon ### END INIT INFO After 'insserv -d apt-cacher-ng', bind9 starts at S17 and apt-cacher-ng at S18. regards Richard Boardman -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
