fetch fails, ftp works question
Barbish3 at adelphia.net
Mon Feb 2 06:40:20 PST 2004
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
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.
From: owner-freebsd-questions at freebsd.org
[mailto:owner-freebsd-questions at freebsd.org]On Behalf Of Ion-Mihai
Sent: Monday, February 02, 2004 7:26 AM
To: freebsd-questions at freebsd.org
Subject: fetch fails, ftp works question
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
It usually work ok on make fetch. But sometimes it doesn't, e.g.
.tar.gz: File unavailable (e.g., file not found, no access)
However the following works:
Can somebody enlighten me ?
Unregistered ;) FreeBSD user
freebsd-questions at freebsd.org mailing list
To unsubscribe, send any mail to
"freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions