From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14138 invoked from network); 24 May 2001 14:42:03 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 24 May 2001 14:42:03 -0000 Received: (qmail 22604 invoked by alias); 24 May 2001 14:41:52 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 14472 Received: (qmail 22590 invoked from network); 24 May 2001 14:41:51 -0000 From: "Bart Schaefer" Message-Id: <1010524144033.ZM13158@candle.brasslantern.com> Date: Thu, 24 May 2001 14:40:33 +0000 In-Reply-To: <3B0D15EF.AF9935D5@u.genie.co.uk> Comments: In reply to Oliver Kiddle "zftp annoyance" (May 24, 3:08pm) References: <3B0D15EF.AF9935D5@u.genie.co.uk> X-Mailer: Z-Mail (5.0.0 30July97) To: Oliver Kiddle , zsh-workers@sunsite.dk Subject: Re: zftp annoyance MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On May 24, 3:08pm, Oliver Kiddle wrote: } Subject: zftp annoyance } } Unfortunately, every time the connection times out and zftp reconnects } the transfer type is reverting to ASCII. Surely it ought to be restoring } the transfer type when it reconnects? How are you managing reconnect on timeout? Using zfautocheck? Looks like the zfconfig parameter maintained by the function system should be storing the transfer type, which it isn't. } This may just be something related to the particular ftp server The doc (for raw zftp, not the function system) says: The FTP default for a transfer is ASCII. However, if zftp finds that the remote host is a UNIX machine with 8-bit byes, it will automatically switch to using binary for file transfers upon open. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net