Well, without actually digging into the guts of the process I would say
that each time something is added to the rpm database that it would
probably be a good idea to do an rpm --rebuilddb to ensure that it remains
clean and in good order. Since everytime something new is installed using
an rpm the database itself, or rather it's content is changed doing at
least a weekly or monthly rpm --rebuild would be at least prudent system
maintenence. Good idea Nick!
That may explain some of the weirdness I'm experiencing while doing the
Mandrake Updates. I"ll have to give that a try.
--
Mark
"If you don't share your concepts and ideals, they end up being worthless,"
"Sharing is what makes them powerful."
On Tue, 30 Jan 2001, Nick Thompson wrote:
> Date: Tue, 30 Jan 2001 15:56:51 +0000
> From: Nick Thompson <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: [expert] Guarddog RPM problems
>
> I don't think this is a problem with that specific RPM as I oftern seem to get the
>same problem when using rpm or Mandrake Update. rpm seems to get stuck at about 99.9%
>CPU basically for ever - I waited 30mins
> before resetting my box. Each time I retry I get the same result. Eventually I
>figured out that an 'rpm --rebuilddb' fixed the problem for that one time, but it
>keeps reoccuring. Why would that happen?
>
> On Sun, 28 Jan 2001, Joseph Markham wrote:
>
> > > Date: Sun, 28 Jan 2001 09:45:31 +0100
> > > From: Joseph Markham <[EMAIL PROTECTED]>
> > > To: [EMAIL PROTECTED]
> > > Subject: [expert] Guarddog RPM problems
> > >
> > > After installing the Guarddog RPM using the KDE RPM Manager on my LM7.2, my HDD
>went into a frenzy virtually locking up my PC. I waited for 15 minutes then did a
>reset as I could not get out of the process.
> > >
> > > Anybody has any ideas?
>
>
>
