From owner-freebsd-current Thu Oct 1 09:56:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21589 for freebsd-current-outgoing; Thu, 1 Oct 1998 09:56:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21572 for ; Thu, 1 Oct 1998 09:56:39 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from mercury (mercury [129.127.36.44]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id CAA13158 for ; Fri, 2 Oct 1998 02:26:18 +0930 (CST) Received: from localhost by mercury; (5.65v3.2/1.1.8.2/27Nov97-0404PM) id AA21925; Fri, 2 Oct 1998 02:26:14 +0930 Date: Fri, 2 Oct 1998 02:26:11 +0930 (CST) From: Kris Kennaway To: current@FreeBSD.ORG Subject: fetch -p Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When using fetch -p to download ports distfiles in passive mode, I consistently get files with the last few hundred bytes missing, and have to go and finish the transfer manually. Has anyone else seen this behaviour? Incidentally (and unrelatedly), the most recent download (which eventually became truncated) fairly stormed down my modem - I averaged 1.63k/s on my 14.4k modem for the transfer of MesaLib-3.0.tar.gz, which gzip -9 was only able to shrink by .9%. This transfer _did_ spam the absolute heck out of me - I got lags of about a minute on my telnet session active at the time, but is it really feasible to get this kind of performance out of a 14.4k modem (including the protocol overhead?), or is fetch a bit off on its' bandwidth calculation? Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message