Re: rh-rpm] Lockup safety in rpm-4.1.1 and rpm-4.2

[seth vidal <skvidal phy duke edu>]

> 
> > Should apt, yum and other package managers be forbidden from aborting at
> > certain types like rpm?  (CTRL-C doesn't do anything.) 
> 
> It would certainly help matters.  but of course yum and the
> apt- stuff are not under Red Hat's control.  
> 
> The issue of two competing processes and mututal ( although
> not always a 'deadly')  embrace when more than one process is
> in the RPM database remain an issue.
> 
> [I _don't_ ctrl-C yum, and strive to run only one RPM related
> process at once, but in a very high load situation, I had an
> embrace of the cronned yum process and a manual rpm process
> lock up RPM just last Friday.  Not really repoduceable,
> unfortunately.]

Jeff told me a way to solve this.

if I can detect a lockup then kill the locks and it should free itself.

if I can't detect the lock I should just kill the lock files before
running the transaction set.

that's what I intend to do.

-sv