Hi, On Fri, Mar 20, 2015 at 10:27:36AM +1300, Jason Haar wrote: > Telling users what to do is fine and sensible, but has a 0% chance of > working. Wouldn't it be better than openvpn checks the state of the > interface right at the beginning and simply refuses to connect if it's > in an unusable state? I'd rather the client went into an infinite loop > of starting, checking, exiting, starting, etc than involve the server > (which affects other users). A 5-10 second delay after such a condition > was detected would help reduce any client impact too of course
Not actually wanting to test on windows - would you have a log file
for me that shows the particular error, so we could just add a delay
there? That would be a one-line fix that could easily go into 2.3.7 :)
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
pgpUn5x_z4KKr.pgp
Description: PGP signature
------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
