Date: Mon, 20 Jan 1997 00:17:10 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: FreeBSD-bugs@freefall.freebsd.org Subject: Re: bin/2528: fetch(1)'s timeout is ridiculously short Message-ID: <Mutt.19970120001710.j@uriah.heep.sax.de> In-Reply-To: <9701192239.AA13184@cabri.obs-besancon.fr>; from Jean-Marc Zucconi on Jan 19, 1997 23:39:26 %2B0100 References: <199701191110.DAA27226@freefall.freebsd.org> <9701192239.AA13184@cabri.obs-besancon.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
As Jean-Marc Zucconi wrote: > Maybe, but I have seen ftp sessions which never end. Not after 4 > hours, not even after 4 days. But then, the TCP connection was probably still alive, but the upper layers did no longer respond. > And you can always 'export FTP_TIMEOUT=14400'. No. I was voting for a saner default value. Something like at least half an hour. A value in the range of a few minutes might be okay if you've got a T3 at home, but if you depend on a modem that occasion- ally can drop carrier, it's impractical. In this case, 2/3 of the sheer amount of data have already been arrived by the time fetch thought it should abort. Of course, all this is only referring to an already _established_ connection. The timeout for the initial connection is okay. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Mutt.19970120001710.j>