On Sat, Jun 11, 2016 at 4:26 PM, Gert Doering <g...@greenie.muc.de> wrote:
> On Sat, Jun 11, 2016 at 02:47:47PM -0400, Selva Nair wrote: > > Isn't this controlled by the http-proxy-retry option which is off by > > default? Set that in the config and SIGUSR1 restart should happen, I > > think... > > Right you are, and ditto for --socks-proxy-retry. > > Sat Jun 11 22:23:50 2016 Attempting to establish TCP connection with > [AF_INET]195.30.4.1:23 [nonblock] > Sat Jun 11 22:23:51 2016 TCP connection established with [AF_INET] > 195.30.4.1:23 > Sat Jun 11 22:23:51 2016 Send to HTTP proxy: 'CONNECT 10.0.0.1:51196 > HTTP/1.0' > Sat Jun 11 22:23:51 2016 Send to HTTP proxy: 'Host: 10.0.0.1' > Sat Jun 11 22:24:10 2016 recv_line: TCP port read timeout expired: > Operation now in progress (errno=115) > Sat Jun 11 22:24:10 2016 SIGUSR1[soft,init_instance] received, process > restarting > Sat Jun 11 22:24:10 2016 Restart pause, 5 second(s) > [..] > Sat Jun 11 22:24:15 2016 Attempting to establish TCP connection with > [AF_INET]195.30.4.1:23 [nonblock] > > > (Side note: you win the "who knows more obscure/rarely used OpenVPN > options" > contest today :-) ) > I respectfully decline to accept..:-) I've been scruitinizing every SIGsomething in the code as a part of my foray into "Signals in OpenVPN", saw this option only the other day for the first time.. > > I do wonder how useful these settings are, and why they are not default... > they predate my OpenVPN involvement by many years. No clue.. Selva
