rpm all wacked?

[Vladimir G. Ivanovic]

Whenever I have RPM problems of any sort (hang, errors) I immediately
delete the __db.00{1,2.3} files (usually) in /var/lib/rpm:

   rm /var/lib/rpm/__db.00*

If that doesn't help, I rebuild the RPM database:

   rpm --rebuilddb

--- Vladimir

------------------------------------------------------------------------
Vladimir G. Ivanovic                        http://leonora.org/~vladimir
2770 Cowper St.                                         vladimir at acm.org
Palo Alto, CA 94306-2447                                 +1 650 678 8014
------------------------------------------------------------------------

>>>>> "fs" == Fred Shaul <info at zaptech.com> writes:

    fs> When I try simple rpm commands, and or invoke them using up2date getting
    fs> errors ...
    fs> 
    fs> Help!
    fs> 
    fs> # rpm -qa
    fs> rpmdb: unable to join the environment
    fs> error: db4 error(11) from dbenv->open: Resource temporarily unavailable
    fs> error: cannot open Packages index using db3
    fs>    - Resource temporarily unavailable (11)
    fs> error: cannot open Packages database in /var/lib/rpm
    fs> no packages
    fs> 
    fs> 
    fs> # uname -a
    fs> Linux bilbo.scalix.local 2.4.22-1.2115.nptl #1
    fs> Wed Oct 29 15:42:51 EST 2003 i686
    fs> i686 i386 GNU/Linux
    fs> 
    fs> # cat /etc/fedora-release
    fs> Fedora Core release 1 (Yarrow)
    fs> 
    fs> 
    fs> -- 
    fs> fedora-list mailing list
    fs> fedora-list at redhat.com
    fs> To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    fs>