From owner-freebsd-ports Wed Jul 12 3:34:38 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 DB1CC37B6FA; Wed, 12 Jul 2000 03:34:30 -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 MAA84886; Wed, 12 Jul 2000 12:34:25 +0200 (CEST) (envelope-from des@flood.ping.uio.no) To: Will Andrews Cc: Adam , Satoshi - Ports Wraith - Asami , ports@FreeBSD.ORG Subject: Re: fetch(1) timeout References: <20000712055707.C1690@argon.gryphonsoft.com> <20000712061459.D1690@argon.gryphonsoft.com> From: Dag-Erling Smorgrav Date: 12 Jul 2000 12:34:24 +0200 In-Reply-To: Will Andrews's message of "Wed, 12 Jul 2000 06:14:59 -0400" Message-ID: Lines: 23 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 Will Andrews writes: > On Wed, Jul 12, 2000 at 12:07:45PM +0200, Dag-Erling Smorgrav wrote: > > That's not very helpful, you know. Do you have something constructive > > to add, such as a detailed description of your problem with -r? > Sorry, I intended that to be a wakeup call. Of course I have something > more helpful: > [...] The first time around, you killed fetch(1), so it never had a chance of setting the modification time on the file. The second time around, it noticed that the local file had a modification time different from that of the remote file, and decided not to resume the transfer. This is expected and documented behaviour; to force fetch(1) to disregard the modification time when considering whether or not to resume a transfer, use the -F option. It is possible to modify fetch(1) so it will set the modification time even if interrupted; I will consider doing so if the changes required are not too intrusive. 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