[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: rpm lockups - argh

Hash: SHA1

On Tue, 23 Sep 2003 21:32:24 +1000, Paul Gear wrote:

> Michael Schwendt wrote:
> > ...
> > Can you describe your usual RPM activities?
> > 
> > Do you interrupt rpm often? Interrupting rpm is one major source of
> > being confronted with stale lock files. 
> Why should that make any difference?  If rpm can't handle being
> interrupted, that means that it is too fragile for the job.  Handling
> user interrupts is one of the most important features rpm can have.
> Of course, i'm not saying that this makes the problem any easier to
> solve, but to require that people never interrupt rpm is to require that
> they never make mistakes, and we all do that...

Interestingly, nobody requires the user to not interrupt rpm.

[I don't know why I reply to your comment at all. Maybe you don't
even want to understand me. ;)]

The difference is that you can avoid frequent lockups when you know
what triggers them or what makes them more likely to occur. Similarly,
knowledge of the "rm -f /var/lib/rpm/__db* ; rpm -vv --rebuilddb" fix
helps most users, too. And the average user is glad about such a
work-around once he has managed to run into the rpm lockup trap.

*I*'m not asking anyone to stop complaining. Complain as loud as you
can if you feel it's necessary. Look up the corresponding bug reports
at bugzilla.redhat.com. Phone up Red Hat customer support and voice
your concerns.

- -- 
Version: GnuPG v1.2.3 (GNU/Linux)


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]