Ralph Shumaker wrote:
I decided to try something different. Frequently (for the last month or so), trying to do anything with yum requires the switch "--disablerepo=rpmforge". The first time I encountered the problem, the header from rpmforge would get about 70k before it died. And it was consistent like that for many days. Then one day (right after posting the problem to a kplug forum) it started working. But that was short-lived and started doing the same thing again but this time choking consistently at 124k.

But I'm tired of using that switch, so I decided to try to get the header file another way. Firefox choked at about the same place. But then Firefox would not try again. I'd click on the file, but nothing would happen after the first time. So I tried with Konqueror.

With Konqueror, at 12%, I got a dialog telling me that the connection was broken. So I clicked on the file again, and Konqueror gave me the option to resume. I chose that option. Then the same thing happened at 24%. Then again at 36%, 48%, 60%, 72%, 85%, and finally 97%. The next resume grabbed the rest.

I am about to chown the file to root:root and move the file into the appropriate yum directory and see if it works (it does). I'm a little concerned that the file is the result of *8* resumes. 8 breaks in the download. I hope the resume function is reliable (seems ok).

But what intrigues me is that each choke was every 12.?%, because that is just too consistent to be coincidence.

Any ideas?

Why don't you just set enabled=0 in the /etc/yum.repos.d/rpmforge.repo file to reflect that you don't want to use the rpmforge repository by default? If you do that, then if you DO want to use the repository, you use it like this:

# yum --enablerepo=rpmforge install some-software-package

One thing you should so is clean out the yum cache, because it sometimes gets munged and starts to act weird.

# yum clean all

The next time you run yum it will download all the header files again and rebuild its cache.

Gus

--
KPLUG-Newbie@kernel-panic.org
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie

Reply via email to