From owner-freebsd-ports Wed Jul 12 2:31: 8 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 88B1A37BC22; Wed, 12 Jul 2000 02:30:59 -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 LAA84634; Wed, 12 Jul 2000 11:30:57 +0200 (CEST) (envelope-from des@flood.ping.uio.no) To: asami@freebsd.org (Satoshi - Ports Wraith - Asami) Cc: ports@freebsd.org Subject: Re: fetch(1) timeout References: From: Dag-Erling Smorgrav Date: 12 Jul 2000 11:30:56 +0200 In-Reply-To: asami@freebsd.org's message of "12 Jul 2000 02:12:40 -0700" Message-ID: Lines: 13 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 asami@freebsd.org (Satoshi - Ports Wraith - Asami) writes: > Adding a timeout value is fine, but isn't 60 seconds a tad too short? :) I don't think so; the timeout value only applies to time spent waiting for data from the server in command mode, not to total time spent fetching the file. Receipt of any data at all from the server resets the timeout, so if the server spends 40 seconds reacting to the PASV command, and then 40 seconds reacting to the RETR command, libfetch will not time out, even though the total exceeds 60 seconds. 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