Michael, Thanks to you, Tom Diehl, and (just) Joe for clearing this up for me. After figuring out I needed to upgrade beecrypt to get libbeecrypt.so.6, I upgraded to beecrypt-*3.0.1-0.20030630.1, popt-1.8.1-0.11, and rpm-*4.2.1-0.11 from rawhide. I too am puzzled as to why Red Hat would permit one of their key utilities -- make that their premier TRADEMARK utility -- to deteriorate like this without aggressively pursuing an errata upgrade. --Doc Savage Fairview Heights, IL On Mon, 2003-07-07 at 16:08, M A Young wrote: > On Mon, 7 Jul 2003 dsavage@xxxxxxxxxxx wrote: > > > > Here rpm stalls. For hours. Until I kill it. Delete the > > /var/lib/rpm/__db* files and run 'rpm --rebuilddb' (ignoring the bogus > > 'error: db4 error(16) from dbenv->remove: Device or resource busy' > > message). > > > > ... > > > > Has anyone else noticed this behavior with rpm-4.2-0.69? It appears that > > something is corrupting my database between uses. > > The database isn't corrupt, just locked with a stale lock. Removing the > __db files is probably enough to free the system, rebuilding is likely to > be superfluous. The rpm packages from www.rpm.org, and presumably also > those from rawhide should be less prone to hang. > > Michael Young >
