Date: Sun, 19 Jan 1997 12:06:02 +0100 (MET) From: J Wunsch <j@uriah.heep.sax.de> To: FreeBSD-gnats-submit@freebsd.org Subject: bin/2528: fetch(1)'s timeout is ridiculously short Message-ID: <199701191106.MAA15730@uriah.heep.sax.de> Resent-Message-ID: <199701191110.DAA27226@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 2528 >Category: bin >Synopsis: fetch(1)'s timeout is ridiculously short >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sun Jan 19 03:10:01 PST 1997 >Last-Modified: >Originator: J Wunsch >Organization: >Release: FreeBSD 3.0-CURRENT i386 >Environment: (irrelevant) >Description: >How-To-Repeat: Drop modem carrier while fetching something. >Fix: Don't imply a timeout of its own. A TCP connection has a timeout in the range of 4 hours, and i fail to see a reason why an application should abort an otherwise intact TCP connection. We are not Windows. :-) >Audit-Trail: >Unformatted: >> Attempting to fetch from ftp://freefall.freebsd.org/pub/CVSup/. Receiving cvsup-14.1.1.tar.gz (197045 bytes): 67% fetch: Timeout >> Couldn't fetch it - please try to retrieve this >> port manually into /usr/ports/distfiles/ and try again. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. My ISP's link dropped carrier, and i had to wait a minute or two until their machine was up again. (Since i'm also my ISP, i know that we've got crappy hardware there. :) After redialing, see above. fetch gave up, and aborted the intact TCP connection.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701191106.MAA15730>