Re: [Bug-wget] retry_connrefused?

2018-04-10 Thread Jeffrey Fetterman
There is so much crap in stdin that the text file for the debug output is so big I can't even open it. It only occurs on occasion, I can't replicate it reliably. On Tue, Apr 10, 2018 at 3:27 PM, Tim Rühsen wrote: > > > On 10.04.2018 20:37, Jeffrey Fetterman wrote: > > with

Re: [Bug-wget] retry_connrefused?

2018-04-10 Thread Tim Rühsen
On 10.04.2018 20:37, Jeffrey Fetterman wrote: > with --tries=5 set, Failed to connect (111) will still instantly abort the > operation. As I wrote, not reproducible here (see my debug output). Please append your debug output. Regards, Tim > On Tue, Apr 10, 2018 at 2:45 AM, Tim Rühsen

Re: [Bug-wget] retry_connrefused?

2018-04-10 Thread Jeffrey Fetterman
500 internal server error isn't being re-tried either. On Tue, Apr 10, 2018 at 2:45 AM, Tim Rühsen wrote: > On 04/10/2018 03:12 AM, Jeffrey Fetterman wrote: > > --retry_connrefused is mentioned in the documentation but it doesn't seem > > to be an option anymore. I can't

Re: [Bug-wget] retry_connrefused?

2018-04-10 Thread Jeffrey Fetterman
with --tries=5 set, Failed to connect (111) will still instantly abort the operation. On Tue, Apr 10, 2018 at 2:45 AM, Tim Rühsen wrote: > On 04/10/2018 03:12 AM, Jeffrey Fetterman wrote: > > --retry_connrefused is mentioned in the documentation but it doesn't seem > > to

Re: [Bug-wget] retry_connrefused?

2018-04-10 Thread Tim Rühsen
On 04/10/2018 03:12 AM, Jeffrey Fetterman wrote: > --retry_connrefused is mentioned in the documentation but it doesn't seem > to be an option anymore. I can't find a replacement for it, either. My VPN > is being a bit fussy today and I keep having to restart my script because > of 111 errors. >