From owner-freebsd-ports Wed Jul 12 2:54:55 2000 Delivered-To: freebsd-ports@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id D486A37BD10; Wed, 12 Jul 2000 02:54:49 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id LAA84720; Wed, 12 Jul 2000 11:54:41 +0200 (CEST) (envelope-from des@flood.ping.uio.no) To: Adam Cc: Satoshi - Ports Wraith - Asami , ports@FreeBSD.ORG Subject: Re: fetch(1) timeout References: From: Dag-Erling Smorgrav Date: 12 Jul 2000 11:54:41 +0200 In-Reply-To: Dag-Erling Smorgrav's message of "12 Jul 2000 11:52:46 +0200" Message-ID: Lines: 16 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dag-Erling Smorgrav writes: > Adam writes: > > What if something like your internet connection becomes intermittant > > and drops for 3 minutes (ISP screwed route, cable modem/dsl unit > > resets, janitor trips over ethernet) and you return with the same ip? If > > you were 95% done downloading XFree86 at 2k/sec(bad net day?) and it timed > > out at 60 seconds that would be pretty dissapointing. Maybe a printf > > warning at 60 seconds informing of a future impending drop? (or not) > That's what -r is for. And BTW, if you're offline for three minutes, the sending side will already have timed out before you reconnect. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message