This sounds like a Tunnelblick failure. I'd suggest checking with them first, they do all sorts of things with scripts and such.
Cheers ----- Eric F Crist On Oct 21, 2012, at 17:40:08, Jonathan K. Bullard <jkbull...@gmail.com> wrote: > A Tunnelblick user has reported odd behavior with name resolution failures. I > can't tell if it is a bug in OpenVPN, a bug in the documentation, or > something else. The behavior is apparently the same in OpenVPN 2.2.1 and > 2.3alpha1. > > The 2.3 man page says: > --resolv-retry n > If hostname resolve fails for --remote, retry resolve for n seconds > before failing. > Set n to "infinite" to retry indefinitely. > By default, --resolv-retry infinite is enabled. You can disable by > setting n=0. > > But the behavior seems very different: > > If a name resolution failure (caused, for example, by losing the network > connection) occurs > and --resolv-retry is: > 1, the first resolution failure terminates the connection; > 5, resolution attempts are made dozens of times per second, seemingly > forever; or > 10, resolution attempts are made every five seconds, seemingly forever. > > Any ideas if this is a program bug, a documentation bug, or something else, > for example, a problem that only occurs on OS X? > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct_______________________________________________ > Openvpn-devel mailing list > Openvpn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openvpn-devel
