Re: fetch fails, ftp works question
On Mon, 2 Feb 2004 09:40:12 -0500 "JJB" <[EMAIL PROTECTED]> wrote: > FBSD Friend Thanks for your time, > Since the fetch command does function for you, but some times you > get this message, > File unavailable (e.g., file not found, no access) > > The "file not found" part you know is not true, because you have > used the same command where it does get the same named package. > SO it must be the "no access" part of the message that has meaning > for this execution of the command. > > That means that the FTP server you are using is busy right them when > you are trying to access it. Like in max users exceeded. Those FTP > servers are being beat on right now by people trying to get the bug > infested 5.2 .iso files. >From that machine's inetd.conf: ftp stream tcp nowait root/usr/libexec/ftpd ftpd -d -l -l -t 120 -T 120 and I don't remember setting any other limits, in other places. > I know the error message is not very clear, but that 's what it > means in your case. Bottom line is since the fetch command works > some times, it can not be fetch command syntax, ether the targeted > server is busy and just try again in 10 seconds, or the you have the > package name typed wrong and it's really not found as you have it > spelled. The second can be, as it is a part of make fetch && make checksum from a script. > The package names with the version number appended as an suffix is [..] > link file commands. I'm talking about distfiles, not packages, so that is not the problem. There can be cases when my host has a newer distinfo the the server, but I've triple-checked that it is not the case here. > One other gotya, for native FBSD without any FTP environment > overrides, ftp defaults to active mode and fetch ftp defaults to > passive mode. >From ftp(1) it defaults to passive. But fetch defaults indeed to active, so this could be a reason; I still don't understand why it works on some ports and not on others. > You will get the "File unavailable (e.g., file not > found, no access)" message if your firewall is blocking FTP access. > Check out this web site for real good explanation of the 2 FTP > access modes http://www.slacksite.com/other/ftp.html > > I hope this gives you the insight you were desiring. > > Joe -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: fetch fails, ftp works question
FBSD Friend
Since the fetch command does function for you, but some times you
get this message,
File unavailable (e.g., file not found, no access)
The "file not found" part you know is not true, because you have
used the same command where it does get the same named package.
SO it must be the "no access" part of the message that has meaning
for this execution of the command.
That means that the FTP server you are using is busy right them when
you are trying to access it. Like in max users exceeded. Those FTP
servers are being beat on right now by people trying to get the bug
infested 5.2 .iso files.
I know the error message is not very clear, but that 's what it
means in your case. Bottom line is since the fetch command works
some times, it can not be fetch command syntax, ether the targeted
server is busy and just try again in 10 seconds, or the you have the
package name typed wrong and it's really not found as you have it
spelled.
The package names with the version number appended as an suffix is
intended for internal ftp server use. The pkg_add -rv command uses
the fetch command to get the latest version of the package by just
using the package name without the version number suffix. The only
sure way to find the correct spelling of the pkg_add package name is
to FTP to the same path location as the pkg_add command uses and
manually find it your self. You will see that all the category
directories contain links to the "all" directory which contains the
packages with names that have the version suffix. The "Latest"
directories which is where pkg_add is pointed, points back to the
"ALL" directory. The same directory tree architecture is used for
all the package-FBSD version directories. That way only an single
"All" directory is created and all FBSD version package directories
end up using the most current package available with the least
amount of work for the ftp site administrator. It's all done using
link file commands.
One other gotya, for native FBSD without any FTP environment
overrides, ftp defaults to active mode and fetch ftp defaults to
passive mode. You will get the "File unavailable (e.g., file not
found, no access)" message if your firewall is blocking FTP access.
Check out this web site for real good explanation of the 2 FTP
access modes http://www.slacksite.com/other/ftp.html
I hope this gives you the insight you were desiring.
Joe
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Ion-Mihai
Tetcu
Sent: Monday, February 02, 2004 7:26 AM
To: [EMAIL PROTECTED]
Subject: fetch fails, ftp works question
Hi,
I have the feeling this is in some FAQ, but I don't understand it.
I have a ftp server on which I have the distfiles and I'm using it
as
MASTER_SITE_OVERRIDE=ftp://user:[EMAIL PROTECTED]/pub/FreeBSD/ports/distfile
s/${DIST_SUBDIR+DIST_SUBDIR/}
It usually work ok on make fetch. But sometimes it doesn't, e.g.
fetch
ftp://user:[EMAIL PROTECTED]/pub/FreeBSD/ports/distfiles/MailScanner-4.25-14
.tar.gz
fetch:
ftp://user:[EMAIL PROTECTED]/pub/FreeBSD/ports/distfiles/MailScanner-4.25-14
.tar.gz: File unavailable (e.g., file not found, no access)
However the following works:
ftp
ftp://user:[EMAIL PROTECTED]/pub/FreeBSD/ports/distfiles/MailScanner-4.25-14
.tar.gz
Can somebody enlighten me ?
--
IOnut
Unregistered ;) FreeBSD user
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
"[EMAIL PROTECTED]"
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fetch fails, ftp works question
On Mon, 02 Feb 2004 15:02:40 +0200
Nelis Lamprecht <[EMAIL PROTECTED]> wrote:
> On Mon, 2004-02-02 at 14:25, Ion-Mihai Tetcu wrote:
> > Hi,
> >
> > I have the feeling this is in some FAQ, but I don't understand it.
> >
> > I have a ftp server on which I have the distfiles and I'm using it
> > as
> > MASTER_SITE_OVERRIDE=ftp://user:[EMAIL PROTECTED]/pub/FreeBSD/ports/distfil
> > es/${DIST_SUBDIR+DIST_SUBDIR/}
> >
> > It usually work ok on make fetch. But sometimes it doesn't, e.g.
> > fetch
> > ftp://user:[EMAIL PROTECTED]/pub/FreeBSD/ports/distfiles/MailScanner-4.25-14.tar.gz
> > fetch:
> > ftp://user:[EMAIL
> > PROTECTED]/pub/FreeBSD/ports/distfiles/MailScanner-4.25-14.tar.gz:
> > File unavailable (e.g., file not found, no access)
> >
> > However the following works:
> > ftp
> > ftp://user:[EMAIL PROTECTED]/pub/FreeBSD/ports/distfiles/MailScanner-4.25-14.tar.gz
> >
> > Can somebody enlighten me ?
>
> Try using the FTP_LOGIN and FTP_PASSWORD variables.
The odd thing is that for some ports it works and for some it doesn't,
so I don't think is an authentication problem.
> If all else fails you can try the FETCH_CMD variable in /etc/make.conf
> and change it to use ftp, wget etc.
Yes, I'm trying that also; the problem is that, if I use:
FETCH_CMD=/usr/bin/ftp
FETCH_BEFORE_ARGS=-v
some fetching fails because ftp gets passed an -S option (I presume for
the files that have the new SIZE in the distinfo). The same for axel,
etc.
The hole infrastructure is based on the assumption
FETCH_CMD=/usr/bin/fetch
( and FETCH_BEFORE_ARGS=ARr )
and I found no way to override passing '-S'.
> Oh, not sure if that was a typo above but it should be:
> MASTER_SITE_OVERRIDE?=
> ftp://user:[EMAIL PROTECTED]/pub/FreeBSD/ports/distfiles/${DIST_SUBDIR}/
Why ?
${DIST_SUBDIR+DIST_SUBDIR/} will expand in DIST_SUBDIR with an ending
'/' if $DIST_SUBDIR is set and will be blank otherwise. If I use
${DIST_SUBDIR}/ the ending slash will be added even if the distfile is
in /usr/ports/distfiles/ (== pub/FreeBSD/ports/distfiles/) e.g.
pub/FreeBSD/ports/distfiles//my_distfile and the fetch will fail.
Theoretically on the 'host' machine I should have all the distfiles, so
I want all downloads to be made from there. I don't remember what the
'?=' means.
Thanks,
--
IOnut
Unregistered ;) FreeBSD user
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fetch fails, ftp works question
On Mon, 2004-02-02 at 14:25, Ion-Mihai Tetcu wrote:
> Hi,
>
> I have the feeling this is in some FAQ, but I don't understand it.
>
> I have a ftp server on which I have the distfiles and I'm using it as
> MASTER_SITE_OVERRIDE=ftp://user:[EMAIL
> PROTECTED]/pub/FreeBSD/ports/distfiles/${DIST_SUBDIR+DIST_SUBDIR/}
>
> It usually work ok on make fetch. But sometimes it doesn't, e.g.
> fetch ftp://user:[EMAIL
> PROTECTED]/pub/FreeBSD/ports/distfiles/MailScanner-4.25-14.tar.gz
> fetch: ftp://user:[EMAIL
> PROTECTED]/pub/FreeBSD/ports/distfiles/MailScanner-4.25-14.tar.gz: File unavailable
> (e.g., file not found, no access)
>
> However the following works:
> ftp ftp://user:[EMAIL
> PROTECTED]/pub/FreeBSD/ports/distfiles/MailScanner-4.25-14.tar.gz
>
> Can somebody enlighten me ?
Try using the FTP_LOGIN and FTP_PASSWORD variables. If all else fails
you can try the FETCH_CMD variable in /etc/make.conf and change it to
use ftp, wget etc. Oh, not sure if that was a typo above but it should
be:
MASTER_SITE_OVERRIDE?=
ftp://user:[EMAIL PROTECTED]/pub/FreeBSD/ports/distfiles/${DIST_SUBDIR}/
Regards,
--
Nelis Lamprecht
PGP: http://www.8ball.co.za/pgp/nelis.key
"Unix IS user friendly.. It's just selective about who its friends are."
signature.asc
Description: This is a digitally signed message part
fetch fails, ftp works question
Hi,
I have the feeling this is in some FAQ, but I don't understand it.
I have a ftp server on which I have the distfiles and I'm using it as
MASTER_SITE_OVERRIDE=ftp://user:[EMAIL
PROTECTED]/pub/FreeBSD/ports/distfiles/${DIST_SUBDIR+DIST_SUBDIR/}
It usually work ok on make fetch. But sometimes it doesn't, e.g.
fetch ftp://user:[EMAIL
PROTECTED]/pub/FreeBSD/ports/distfiles/MailScanner-4.25-14.tar.gz
fetch: ftp://user:[EMAIL
PROTECTED]/pub/FreeBSD/ports/distfiles/MailScanner-4.25-14.tar.gz: File unavailable
(e.g., file not found, no access)
However the following works:
ftp ftp://user:[EMAIL PROTECTED]/pub/FreeBSD/ports/distfiles/MailScanner-4.25-14.tar.gz
Can somebody enlighten me ?
--
IOnut
Unregistered ;) FreeBSD user
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
