Chris Carr wrote: > On Tue, 2010-02-02 at 22:45 +0000, Simon Kelley wrote: >> Chris Carr wrote: >>> On Tue, 2010-02-02 at 21:40 +0000, Simon Kelley wrote: >>>> My guess that this is something like vpn provides network and depends on >>>> $named >>>> >>>> dnsmasq provides $named and depends on $network >>> Has this changed recently? I have upgraded dnsmasq without this problem >>> before, since migrating to dependency-based booting. >> The LSB header hasn't changed in dnsmasq forever, but insserv and/or >> openvpn may have changed. Certainly /etc/insserv.conf now defines >> dnsmasq as satisfying $named. >> >>>> Could you let me know what version of openvpn you have, and the contents >>>> of /etc/insserv* >>> chr...@baba:~$ dpkg -l openvpn >>> [snip] >>> ii openvpn 2.1.0-1 virtual private network daemon >>> >>> /etc/insserv is empty: >>> >> I'm not clear what he problem is here. I'm tempted to bump this to insserv. > > Hi there, > > Is there anything I can do or need to do to expedite this? > > Thanks, > > CC
I'm slightly at a loss about what to do next, since I can't reproduce the problem with inserv 1.12.0-14 and openvpn 2.1.0-1 don't really understand how it's supposed to work in the first place. As you have the only current known example of a system which demonstrates this behaviour, can you find any other information? (I'm not sure what: maybe "insserv -v" would be useful) Cheers, Simon. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
