On Mon, 22 Aug 2005, Bryan J. Smith wrote:
> On Mon, 2005-08-22 at 20:31 +0200, Dag Wieers wrote:
> > Beware though, removing the __db.* files (a cache) should be sufficient.
> > You do not have to run rpm --rebuilddb if the cause of the poblem was the
> > corrupt cache.
> > Also, do NOT attempt to run rpm --rebuilddb with a corrupt cache in place,
> > because this may cause your rpmdb to get corrupted. Often people complain
> > that rpm --rebuilddb did not solve their rpmdb problems,
>
> Yep, AFAIK, --rebuilddb hasn't been required since the original RPM 4.1
> (was it?) of Red Hat Linux (RHL) 8. Can you confirm that DAG?
I can't. I just know JBJ often repeated the warning. Also, cache
corruption should not happen on a stable system anymore. Those bugs have
been fixed. But if you do encounter this, try to reproduce, check you
hardware and then contact JBJ.
> > while in fact rpm --rebuilddb corrupted the rpmdb. And a mere removal of
> > the cache (__db.*) was sufficient to solve the problem.
> > You have been warned :)
>
> I often do an "--initdb" instead. Is that wrong? I haven't done it
> since RHL 9.
I am not sure if it has any effect on a system with an existing rpmdb.
Never used it for that.
Kind regards,
-- dag wieers, dag@xxxxxxxxxx, http://dag.wieers.com/ --
[all I want is a warm bed and a kind word and unlimited power]
