On Sun, Jan 20, 2002 at 11:19:17AM -0800, Christopher Mahmood wrote:

[ as always, please don't send stuff like this to the list...sysadmin@suse.com is more appropriate ]

* JW (jw@centraltexasit.com) [020120 10:44]:

...

I've tried wget, nt and kwebget, and all of them fail, I think the 2 guis use wget internally (I know kwebget does).

Why are you using tools designed for http?

I was under impression wget was designed for ftp also. Am I wrong?

...

Anyone have any ideas what else might be wrong? Here's wget's output: /pub/suse/i386/supplementary/KDE/update_for_7.3/experimental ... done. ==> PORT ... done. ==> REST 3317368 ... done. ==> RETR kdebase3-2.91-4.rpm ... Error in server response, closing control connection. Retrying.

You need to use REGET, not a REST with the byte offset.

e.g.,

ftp -a ftp.suse.com cd pub get ls-Ral.txt ^C 426 Transfer aborted. Data connection closed. reget ls-Ral.txt local: ls-Ral.txt remote: ls-Ral.txt : :

Quite interesting. I've been getting the same kind of error with mirror perl package. Mirror (which I installed from 7.3 Pro) uses REST command. Is mirror out of sync with latest developments in ftp protocol? -Kastus

On Monday 21 January 2002 00.56, Praise wrote:

No, and I have been using wget to download from the suse ftp server some days ago. I have been lucky because I took just the moment when it was not overloaded:-)

Are all the mirrors down? Is there a specific reason everyone is using ftp.suse.com instead of doing the sensible thing and using a server physically closer to you? If you go against recommendations you forfeit your right to complain //Anders

On Monday 21 January 2002 03.06, Konstantin (Kastus) Shchuka wrote:

On Mon, Jan 21, 2002 at 01:00:28AM +0100, Anders Johansson wrote:

...

Are all the mirrors down? Is there a specific reason everyone is using ftp.suse.com instead of doing the sensible thing and using a server physically closer to you?

I wish anybody pointed me to a server closer than ftp.suse.com to Walnut Creek, CA. I would gladly use it.

Thank you for your recommendations.

I can't remember recommending anything to you. Praise, on the other hand, is from Italy. If the only people who used ftp.suse.com were from California, I suspect you wouldn't have that much of a bandwidth problem. But as always: thanks for your input. //Anders

On Sun, Jan 20, 2002 at 09:23:24PM -0800, Christopher Mahmood wrote:

* Konstantin (Kastus) Shchuka (kastus@tsoft.com) [020120 18:06]:

...

I wish anybody pointed me to a server closer than ftp.suse.com to Walnut Creek, CA. I would gladly use it.

Thank you for your recommendations.

Er, it's in Oakland CA.

I know. It's less than 30 min. drive from my home. That's why I'm asking if I may use ftp.suse.com or should I look for a *closer* mirror. Thanks, -Kastus

* Charles Philip Chan (karnak@look.ca) [020120 12:21]:

On Sun, 20 Jan 2002 11:19:17 -0800 Christopher Mahmood wrote:

...

[ as always, please don't send stuff like this to the list...sysadmin@suse.com is more appropriate ]

Actually, I think this is a valid discussion for the list.

He's reporting what's potentially a problem with the ftp server--I rarely look at this list on the weekends so if it really was a problem I wouldn't see it. And no, it's not valid for the list. Please send an email to suse-linux-e-faq@suse.com and read it.

...

Why are you using tools designed for http?

Hum, nt (aka Downloader for X) designed for http? For your info, it is designed to do both ftp and http transfers and does support suspend/resume.

Yes, every web browser also claims to be able to do ftp as well as http but 99% of the problems reported to ftpadmin@suse.com are the resulting from people trying to use a browser. -- -ckm

* Charles Philip Chan (karnak@look.ca) [020120 11:30]:

I know, SuSE's ftp site seem to always be overloaded.

yes, it is. Please use a mirror.

The transfer rate is horrible and it keeps starting and stopping.

The rate is limited per connection.

P.S.: I am uploading something to SuSE's incoming directory right now and the transfer rate is averaging around 0.9x KB/s!

That's most likely not our problem but yours...upstream connections to us are rarely slow. Send a traceroute to sysadmin@suse.com if this was supposed to be anything other than a complaint. -- -ckm