On Thu, 2010-03-25 at 17:06 +0000, Simon Kelley wrote: > Chris Carr wrote: > > > > Ironically the problem was the opposite: the Provides: line in > > /etc/init.d/openvpn said openvpn, but I had added a dependency on "vpn" to > > the Required-Start line in /etc/init.d/dnsmasq. Once I changed this to > > "openvpn", it worked. > > > > But my main concern is: should the user have to add that dependency manually > > to make dnsmasq and openvpn work together? Isn't there a way that the > > package configuration can do this automatically? > > > > For me, it works fine without any mention at all of vpn or openvpn in > /etc/init.d/dnsmasq. Is that not the case for you?
Hi Simon, Sorry for the long delay - the server in question only reboots about twice a year, and I have been trying different solutions each time. The short answer is no, I cannot get this to work properly, whatever I do or don't change in /etc/init.d/dnsmasq. The vpn is always the very last thing to start up before gdm, and I don't really understand why. I have not changed /etc/init.d/openvpn since it was installed: ### BEGIN INIT INFO # Provides: openvpn # Required-Start: $network $remote_fs $syslog # Required-Stop: $network $remote_fs $syslog # X-Interactive: true # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Openvpn VPN service ### END INIT INFO Is yours the same? And does your VPN start up before the "starting dnsmasq" message when you boot? I'm very grateful for your continued thoughts on what might be the problem. I wouldn't mind the VPN taking so long to start up if I could make dnsmasq wait for it! Regards, Chris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
