From owner-freebsd-current Tue Mar 16 11:34:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (Postfix) with ESMTP id BBE281550F for ; Tue, 16 Mar 1999 11:33:27 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.3/8.9.3/Kp) with ESMTP id TAA68202; Tue, 16 Mar 1999 19:32:48 GMT Message-ID: <36EEB1E0.75F6C1BB@tdx.co.uk> Date: Tue, 16 Mar 1999 19:32:48 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn Cc: current@freebsd.org Subject: Re: FTP client dies when not in passive mode? References: <67097.921612137@axl.noc.iafrica.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > See the ftp(1) manpage for an explanation. I know about the command line/environment variables that can be used to override this - but it's still annoying (see below)... > In future, please refer general questions related to FreeBSD to the > freebsd-questions mailing list -- freebsd-current is for issues relating > specifically to CURRENT (4.0-CURRENT at the moment). It happens on -current as well as the past versions... I seem to remember someone mentioned it before, but I can't remember the outcome (I think it was mentioned on -current)... Surely it's behaviour should be consistant? - i.e. CTRL-C should abort the current transfer/command (which it does), _unless_ your the other side of a firewall without PASSIVE then CTRL-C does nothing, and your forced to wait, and wait - or dump core... -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message