From owner-freebsd-bugs  Sun Jan 19 14:37:59 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id OAA22196
          for bugs-outgoing; Sun, 19 Jan 1997 14:37:59 -0800 (PST)
Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3])
          by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA22191
          for <FreeBSD-bugs@freefall.freebsd.org>; Sun, 19 Jan 1997 14:37:56 -0800 (PST)
Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C)
	id AA13184; Sun, 19 Jan 97 23:39:26 +0100
Date: Sun, 19 Jan 97 23:39:26 +0100
Message-Id: <9701192239.AA13184@cabri.obs-besancon.fr>
From: Jean-Marc Zucconi <jmz@cabri.obs-besancon.fr>
To: FreeBSD-bugs@freefall.freebsd.org, j@uriah.heep.sax.de
In-Reply-To: <199701191110.DAA27226@freefall.freebsd.org> (message from J
	Wunsch on Sun, 19 Jan 1997 03:10:01 -0800 (PST))
Subject: Re: bin/2528: fetch(1)'s timeout is ridiculously short
X-Mailer: Emacs
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>>>>> J Wunsch writes:
	
 > 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.
 > :-)

Maybe, but I have seen ftp sessions which never end. Not after 4
hours, not even after 4 days.
And you can always 'export FTP_TIMEOUT=14400'.

Jean-Marc
 _____________________________________________________________________________
 Jean-Marc Zucconi       Observatoire de Besancon       F 25010 Besancon cedex
                   PGP Key: finger jmz@cabri.obs-besancon.fr
 =============================================================================