![](https://seccdn.libravatar.org/avatar/bb6f779b889e6015f21e4685227207f9.jpg?s=120&d=mm&r=g)
On Friday 10 January 2003 20:51, Tom Emerson wrote:
On Friday 10 January 2003 11:32 am, netsec novice wrote:
I am consistently getting extremely SLOW response when I attempt to do online updates using Yast (manual or automatic). It sits at the 'Initializing for FTP/HTTP update. One moment please....' for more than an hour sometimes.
This is/was a "boo-boo" on the part of the SuSE developers -- it isn't really "sitting there" -- it is actually doing HUNDREDS of "wget" commands in the background and not reporting the fact that it is "doing anything" (i.e., no "comforting user feedback" was given -- I suspect that this was tested "in house" on a 100megabit or better lan, so for them, the "please wait" was only a few moments...)
I have DSL myself [384k, roughly 40k-bytes/second actual throughput] and it can take several minutes. Be aware that LOTS of people are hitting these servers [many probably automated]. One thing I do that makes me "feel better" is to open a terminal window, "su" to root, and issue the command:
ps x | grep wget
and periodically refresh this with <up-arrow><enter> -- at least, this way I can see which file is being processed and [in some cases] the relative size of the file; likewise, you can do a directory listing of the area YOU uses to store the downloaded files; that gives you an idea of how long it is taking per file...
A mail on this list last year (subject SuSE 8.1 broken?) suggested that you edit /etc/wgetrc and jhange the line #passive_ftp = off by removing the # and changing off to on. Haven't tried it myself though. Pam R -- sed s/MS/Linux/ Linux StepbyStep: http://www.linux-sxs.org/stepbystep.html