Chris Carr wrote: > On 22/03/2010 20:37, Simon Kelley wrote: >> 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) > > Well, I managed to solve the problem, by adding "openvpn" at the end of > the "Required-Start" line in /etc/init.d/dnsmasq. > > I won't close the bug report because I'm not sure how a user would know > that that needed to be done - I only discovered it by some trial and > error. I'm afraid I don't know enough about the service startup logic to > know whether dnsmasq should try to detect the presence of openvpn, or > whether openvpn should really be covered by $network (on which dnsmasq > already depends), or what. The bug may not actually be in dnsmasq. > > Sorry not to be more useful, > > CC > > > What's in the Provides: line in your /etc/init.d/openvpn file? The original error message:
insserv: Service vpn has to be enabled to start service dnsmasq is confusing because a new install of openvpn 2.1.0-1 gives Provides: openvpn. Looking through the changelog for open vpn this changed vpn -> openvpn in openvpn 2.1~rc20-1. If you have an old version of that configfile, it may explain the problem. Cheers, Simon. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
