On Wed, 2006-11-15 at 19:29 -0500, Tony Nelson wrote: > At 6:53 PM -0500 11/15/06, Sam Varshavchik wrote: > >Content-Type: multipart/signed; > > boundary="=_mimegpg-commodore.email-scan.com-28222-1163634835-0005"; > > micalg=pgp-sha1; protocol="application/pgp-signature" > > > >Tony Nelson writes: > > > >> Is there a way to check the RPM database for validity? I know how to > >> rebuild it, and where it is stored, and that when yum says that the > >> database is corrupt that I must do something about it, but is there a way > >> to test it before total failure? > > > >Well, "rpm -q -a -V" is going to go and read pretty much all the bits in the > >rpm database. If something's busted, you're likely going to hit it. > > rpm -Va checks the possibly corrupt database's opinion of the filesystem, > and may be considered a check on the database's accuracy. If RPM doesn't > crash while doing it, nothing much is proved about its validity. > > Is there a tool or command to check the RPM database for being corrupt? > -- > ____________________________________________________________________ > TonyN.:' The Great Writ <mailto:tonynelson@xxxxxxxxxxxxxxxxx> > ' is no more. <http://www.georgeanelson.com/> There are a lot of tools in /usr/lib/rpm/ they are supposed to be called by passing various options to rpm itself. But you can use them directly as well. In your case you could use /usr/lib/rpm/rpmdb_verify you have to give this command the name of the db file to verify. -- Thanx Pritam Ghanghas
