From owner-freebsd-questions Tue Jan 12 12:35:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07691 for freebsd-questions-outgoing; Tue, 12 Jan 1999 12:35:51 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from peloton.physics.montana.edu (peloton.physics.montana.edu [153.90.192.177]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07683 for ; Tue, 12 Jan 1999 12:35:47 -0800 (PST) (envelope-from brett@peloton.physics.montana.edu) Received: from localhost (brett@localhost) by peloton.physics.montana.edu (8.8.8/8.8.7) with SMTP id NAA15585; Tue, 12 Jan 1999 13:32:59 -0700 (MST) (envelope-from brett@peloton.physics.montana.edu) Date: Tue, 12 Jan 1999 13:32:59 -0700 (MST) From: Brett Taylor To: Dan Langille cc: freebsd-questions@FreeBSD.ORG Subject: Re: fetch in passive mode fails (repost) In-Reply-To: <19990112202141.JEYV678125.mta2-rme@wocker> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Dan writes: > I cannot get make to do its fetches in passive mode. As a result, when > doing a make I get errors like this: (snipped) > OK. That tells me fetch is not using passive mode. Running a fetch > with "-p" succeeds. I could just drop the firewall rules and do it > again, but that's not good enough. A read of man fetch tells about an > environment variable: "FTP_PASSIVE_MODE forces the use of passive > mode FTP". I thought it was an environment variable, so I set that. > No effect. I had forgotten about this switch in make.conf so I didn't do that at home where I'm going through a firewall to get out. What I did was edit bsd.port.mk and modified the fetch and ftp commands to use the -p switch. You can edit your bsd.port.mk and look for where FETCH_CMD is defined and change /usr/bin/fetch to /usr/bin/fetch -p. I _know_ this works. Why it doesn't when you set FTP_PASSIVE_MODE in make.conf I don't know. I will go home and try that. One bad thing w/ my solution is you have to fix it everytime you upgrade the bsd.port.*.mk files. Brett ****************************************************************** Brett Taylor brett@peloton.physics.montana.edu http://peloton.physics.montana.edu/brett/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message