On Wed, 1 Nov 2006, seth vidal wrote:
> rm -f /var/lib/rpm/__db*
> rpm --rebuilddb
Yes this was exactly it. yum -d 10 showed the hang was at the rpmdb
read, so I could figure it out.
Is there any reasonable/safe way to make this automagical? Check for
the existence of __db* files at the start of the rpmdb segment and exit
with a warning and instructions on how to fix if it is locked/hung?
Having yum just "go away" forever, immune to Ctrl-C and other mundane
ways of interrupting it puts it (and yumex, which also hangs) beyond the
reach of non-systems-guru type users. With command line yum perhaps
that is a reasonable assumption, but yumex can be run by anyone and a
hard hang (no matter what the cause) is a bug and will lead to immense
frustration on the part of not-so-expert users.
rgb
>
> see if it fixes it.
>
> thanks,
> -sv
>
>
> _______________________________________________
> Yum mailing list
> Yum@xxxxxxxxxxxxxxxxxxxx
> https://lists.dulug.duke.edu/mailman/listinfo/yum
>
--
Robert G. Brown http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567 Fax: 919-660-2525 email:rgb@xxxxxxxxxxxx
