> The latest problem that I just encountered was when installing an rpm. 
> While installing, the rpm program crapped out.  So, I went and killed
> all the rpm process running (I used ps -alh | grep rpm), and proceeded
> to restart the rpm installation.  Same thing happened.  Therefore, I
> then went and tried to do an rpm query to see if it installed at all. 
> The same thing happened (no display, the rpm process just froze).  I
> even tried then to rebuild the database, to no avail.
> 
I have seen this problem when using the Install Packages gui to install
RPMs. I think the gui sometimes locks the RPM database and then hangs
before unlocking it. I have had to kill the gui's python process and
then get rid of the __db.### files (where ### is a three digit number,
ie. __db.001) in /var/lib/rpm. After that any rpm command will work
without requiring a reboot.

So far I have not seen any database corruption from one of these hangs.
I am not entirely sure, but I think this happens more frequently when
trying to install more than one RPM at a time using the gui. Either way,
it is probably safer for now to use the command line to install RPMs.

Hope that helps,
Jon D.



-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to