On Wed, 2004-09-01 at 11:15, seth vidal wrote: > > Then, I delete /var/run/yum.pid and I can run yum manually. > > > > Someone on another list said that it looks like it hangs while trying to > > read from the mirror. Is it possible for a repo to hang a client by not > > replying? > > > > unless your repos are REAAAAAAAAAAAAAAALLY slow, I've found that a hang > in yum is most often caused by an rpmdb lockup. > -sv > This issue was traced to a problem with ftp repos. The hung yum process has an open ftp control connection, with no packets queued for sending - it just sits there keeping yum alive. There's no time out in the ftp code, and no timeout in yum waiting for the ftp. My solution is to release a new default yumconf in the next few weeks with all http repos, because, I'm told, the http code gets 'more luvin'. *shrug* regards, David > > _______________________________________________ > Yum mailing list > Yum@xxxxxxxxxxxxxxxxxxxx > https://lists.dulug.duke.edu/mailman/listinfo/yum -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.dulug.duke.edu/pipermail/yum/attachments/20040901/eebdd4af/attachment-0001.bin
