Filipe Brandenburger wrote on Fri, 11 Jan 2008 10:35:16 -0500:
> You can just remove the __db* files (if you're sure they're there because of
> an
rpm interrupted process, check first if there are no rpm processes running).
__db* are Berkeley DB's lockfiles and are used for transactions inside
Hi,
I used to have exactly the same problem when the machine rebooted in the
middle of an RPM installation or if the rpm process was killed -9.
On Jan 9, 2008 7:41 PM, Kai Schaetzl <[EMAIL PROTECTED]> wrote:
> The process doesn't die, but doesn't seem to do anything
> from that point on. strace
Kai Schaetzl <[EMAIL PROTECTED]> wrote:
Before I do this without need I have a question: if the rpm db is
corrupt shouldn't rpm -q or -qa stop working? Kai
Not necessarily. A regular user can run rpm -q since it doesn't lock
the database (your original posting showed rpm hanging on a FUTEX).
Before I do this without need I have a question: if the rpm db is corrupt
shouldn't rpm -q or -qa stop working?
Kai
--
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
___
CentOS mailing list
CentOS
Kai Schaetzl <[EMAIL PROTECTED]> wrote:
All of a sudden yum hangs on a Centos 4.5 (updated to the latest patch
before 4.6) when I try to use it. "clean metadata" didn't help.
The output of -d5 shows it gets to the point of "Reading Local RPMDB" and
then sits there. The process doesn't die, but
All of a sudden yum hangs on a Centos 4.5 (updated to the latest patch
before 4.6) when I try to use it. "clean metadata" didn't help.
The output of -d5 shows it gets to the point of "Reading Local RPMDB" and
then sits there. The process doesn't die, but doesn't seem to do anything
from that poi
6 matches
Mail list logo
