On Wed, Jul 22, 2009 at 04:01:51PM +0200, Alberto Gonzalez Iniesta wrote: > On Sat, May 05, 2007 at 06:06:07PM +0200, Robert Millan wrote: > > There seems to be a race between daemonised openvpn trying to bring up > > network > > and fetchmail (or the like) trying to connect to a pop server that can only > > be accessed via VPN tunnel. In my particular case, this results in: > > > > - fetchmail not checking mail in its first run. > > - /me being unable to set an high sleep period, since I would have to wait > > too much every time the machine is started. > > > > I assume there could be other (maybe worse) problems because of this. Would > > you consider blocking openvpn initialisation untill the network is brought > > up? > > > Hi Robert, > > I think the solution in this case is in your hands, more than in mine. > You'd probably want to use 'openvpn foobar' in /etc/network/interfaces, > or /etc/ppp/ip-up.d/ to start openvpn only when the network is up. > Instead of having it started on system initialization. > Other option could be starting fetchmail with openvpn's 'up' option > (and up-delay).
Ok, but openvpn installs /etc/init.d/openvpn, shouldn't it hook itself in /etc/network/if-up.d/ instead? -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
