Hi, I don't know too much about insserv, but hendry asked me to write a comment in IRC so here I go :)
Dusan Zatkovsky <msk.c...@gmail.com> writes: > If you are using maradns together with openvpn, and you have specified > marands bind_address to ip address of tun interface, maradns will not > start during boot because tun ifc is not initialized by openvpn yet. I > must fixed it manually renaming /etc/rc2.d/S01maradns to S02. I think both configurations are valid: maradns could depend on openvpn as in your configuration, but openvpn could also rely in DNS to establish a connection. As this depends on the local configuration, this cannot be fixed by adding a additional dependency in the LSB header for the Debian package. (The same holds for using a different Sxx number in the old, non-insserv system.) However, insserv provides a facility to override the LSB header by placing a file with the new LSB header using the same name as the init script in /etc/insserv/overrides (see insserv(8)). I have never done this myself, but please try adding /etc/insserv/ovverides/maradns with the following content: --8<---------------cut here---------------start------------->8--- ### BEGIN INIT INFO # Provides: maradns # Required-Start: $remote_fs $network openvpn # Required-Stop: $remote_fs $network openvpn # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Controls the maradns DNS service ### END INIT INFO --8<---------------cut here---------------end--------------->8--- I don't know whether it is possible to only override single fields so I included all of them to be on the safe side. Regards, Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
