From owner-freebsd-stable Wed Dec 12 2:17:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from bayer2.bayer-ag.de (bayer2.bayer-ag.de [194.120.191.2]) by hub.freebsd.org (Postfix) with SMTP id AF5AA37B417 for ; Wed, 12 Dec 2001 02:17:44 -0800 (PST) Received: from by-inet1.bayer-ag.com (BY17V3.BAYER-AG.COM) by bayer2.bayer-ag.de with SMTP id LAA05337 (SMTP Gateway 4.2 for ); Wed, 12 Dec 2001 11:11:13 +0100 Subject: Antwort: Re: fetch through ftp-proxy =?iso-8859-1?Q?doesn=B4t_work_on_FreBSD_4=2E3-STABLE?= To: Mike Harding Cc: stable@freebsd.org X-Mailer: Lotus Notes Release 5.0.5 September 22, 2000 Message-Id: From: andreas.klemm.ak@bayer-ag.de Date: Wed, 12 Dec 2001 11:16:48 +0100 X-Mimetrack: Serialize by Router on BY-INET1/Central/LEV/DE/BAYER(Release 5.0.8 |June 18, 2001) at 12/12/2001 11:17:44 AM Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thanks, it wasn=B4t clear to me, that ftp goes via http as has been stated out = by somebody other. Thanks, it works now. BTW, do you know a fast ftp mirror program ? Idea: wouldn=B4t it be a good idea to teach fetch recursive ftp (mirror= mode) ? I=B4m behind a firewall and I would prefer to get the 4.4-STABLE source= s without having to burn it at home on CD ... It would be fine, to have a daily updated CVS.tgz and a src.tgz file of= -STABLE sitting somewhere in FreeBSD ftp land for whose who cannot use cvsup. Or is cvsup able to get the sources or cvs deltas via something like ft= p ? ;-) I think no ;-) Andreas /// Mike Harding on 12.12.2001 06:21:44 An: andreas.klemm.ak@bayer-ag.de Kopie: stable@freebsd.org Blindkopie: Thema: Re: fetch through ftp-proxy doesn=B4t work on FreBSD 4.3-STAB= LE It's not very well documented, but if I put the line FETCH_ENV=3D HTTP_PROXY=3D127.0.0.1 in /etc/make.conf, I find that fetch uses squid just fine, at least for ports... I think I had to paw around in the make files for a while to find this = out. - Mike H. From: andreas.klemm.ak@bayer-ag.de Date: Tue, 11 Dec 2001 18:19:26 +0100 X-Mimetrack: Serialize by Router on BY-INET1/Central/LEV/DE/BAYER(Re= lease 5.0.8 |June 18, 2001) at 12/11/2001 06:20:18 PM Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.ORG Hi ! Is it a known issue, that fetch doesn=B4t work via local ftp proxy (= squid) ? I updated the ports collection manually. Everything runs fine, if fetch can get something via http proto. Whenever something should be fetched via ftp proto, it does nothing at all and I get error code 999 (protocol error). In my root=B4s .cshrc I added: setenv FTP_PROXY localhost:3128 setenv FTP_PASSIVE_MODE YES setenv HTTP_PROXY localhost:3128 In /etc/make.conf I configured: HTTP_PROXY=3Dlocalhost:3128 FTP_PROXY=3Dlocalhost:3128 FTP_PASSIVE_MODE=3Dyes In squids logfile I see the successfull fetch attempts via http, but= no single line, when something should be fetched via ftp. In the process status I see, that fetch is executed as follows a) for ftp (doesn=B4t work) 7137 p1 S+ 0:00.01 /usr/bin/fetch -A ftp://ftp.xemacs.org/pub/xemacs/xemacs-21.1/xemacs-21.1.14.tar.gz b) for http (works) /usr/bin/fetch -A http://prdownloads.sourceforge.net/amanda/amanda-2.4.2p2.tar.gz Squids log tells me only something about the fetch using http proto = ... 1008090948.039 34701 127.0.0.1 TCP_MISS/000 560886 GET http://prdownloads.sourceforge.net/amanda/amanda-2.4.2p2.tar.gz - FIRST_UP_PARENT/byfwg5.bayer-ag.com - Is there a bug in FreeBSD 4.3=B4s libfetch ??? Or did I mis-spell a configuration variable ??? Setting FTP_PASSIVE_MODE in .cshrc and /etc/make.conf was only a hac= k, wihout it didn=B4t work as well ... Any comments ??? Thanks Andreas /// Andreas /// To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message = To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message