Your message dated Tue, 19 Nov 2013 21:13:53 +0100 with message-id <[email protected]> and subject line Re: elinks: receive-timeout maximum of 1800 is needlessly short has caused the Debian Bug report #596591, regarding elinks: receive-timeout maximum of 1800 is needlessly short to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 596591: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596591 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: elinks Version: 0.12~pre5-2 The receive-timeout has a maximum of one hour, which seems generous but is actually causing me problems -- I'm starting a long-running backup via an HTML form which doesn't return anything until it's complete, and there are two problems: 1. The backup takes longer than an hour -- I'm just launching it in a screen session and not worrying about how long it takes. Therefore I need a longer timeout 2. For simplicity I've been specifying thousands of hours as the timeout, which seems like it should work. IMHO it should be possible to simply specify an arbitrarily high number (meaning "don't time out ever") without elinks complaining that I've exceeded an unspecified upper limit. I would prefer if the limit were increased to INTEGER_MAX from 1800. I've increased the limit locally (I can construct and send a patch if need be), which seems to work with no problems. Thanks!
--- End Message ---
--- Begin Message ---On Sun, Sep 12, 2010 at 02:34:12PM -0400, Andrew Moise wrote: > Package: elinks > Version: 0.12~pre5-2 > > The receive-timeout has a maximum of one hour, which seems generous > but is actually causing me problems -- I'm starting a long-running > backup via an HTML form which doesn't return anything until it's > complete, and there are two problems: > > 1. The backup takes longer than an hour -- I'm just launching it in a > screen session and not worrying about how long it takes. Therefore I > need a longer timeout > 2. For simplicity I've been specifying thousands of hours as the > timeout, which seems like it should work. IMHO it should be possible > to simply specify an arbitrarily high number (meaning "don't time out > ever") without elinks complaining that I've exceeded an unspecified > upper limit. > > I would prefer if the limit were increased to INTEGER_MAX from 1800. > I've increased the limit locally (I can construct and send a patch if > need be), which seems to work with no problems. > Thanks! The default is perfectly adequate for a browser. I suggest you migrate your backup script to wget or use a local build. Cheers, Moritz
--- End Message ---
