Chris Carr wrote: > > 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 >
The problem seems to have morphed from failure to install packages because of insserv errors, to bad start-up order of daemons. Is that right? There shouldn't be a problem with dnsmasq starting before openvpn, for most common configurations dnsmasq will pick up the existence of the vpn interfaces as they arrive. Cheers, Simon. > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
