From owner-freebsd-stable Tue Jul 25 7:44:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 658C537B697 for ; Tue, 25 Jul 2000 07:44:54 -0700 (PDT) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 53C1A9B3E; Tue, 25 Jul 2000 10:44:53 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 46183BA11; Tue, 25 Jul 2000 10:44:53 -0400 (EDT) Date: Tue, 25 Jul 2000 10:44:53 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Mike Harding Cc: freebsd-stable@freebsd.org Subject: Re: Recent ports behavior (fetch) In-Reply-To: <20000725143107.9A4D1E6E75@netcom1.netcom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Jul 2000, Mike Harding wrote: > > Recently I have noticed that one of the following happens if you > interrupt a fetch during a ports 'make' (say because you have a dialup > and the port is downloading an 18M file): > > 1. Fetch runs in the background and you have to stop it multiple times. > > 2. Fetch leaves a truncated file in /usr/ports/distfiles which much > be deleted by hand. > > Is there any chance for a return to the old behavior (cntl-C stops > fetch, file deleted) for 4.1? It's a lot friendlier for us dial-up > folk... > I brought up (2) last week, with absolutely no response. I too prefer the previous behaviour of deleting truncated files instead of manually deleting them prior to re-fetching a port. ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message