On Thu, Feb 26, 2004, Christian Leber wrote: > Hello, > > when today/yesterday Openpkg 2.0 was released i compiled and installed > it (normal bootstrap) and when i try to use rpm, i get the following: > > [EMAIL PROTECTED] (~) /opt0/cw-2.0/bin/openpkg rpm -qa > rpmdb: mmap: Resource temporarily unavailable > error: db4 error(11) from dbenv->open: Resource temporarily unavailable > error: cannot open Packages index using db3 - Resource temporarily unavailable (11) > error: cannot open Packages database in /opt0/cw-2.0/RPM/DB > no packages > > To be sure I tried on Solaris 8 and 9, didn't help. > Is this a openpkg bug or a problem with the solaris installations i > used? > It is not actually a problem. The new RPM 4.2.1 requires a working locking infrastructure by default. Many NFS installations are not enabled for locking (lockd).
Ralf already mentioned the workaround to change the default to revert to the old RPM 4.0.x behaviour. During bootstrap, a temporary RPM database is created in $TMPDIR. A practial workaround is to point TMPDIR to a local (or any locking enabled) filesysontem. This has been verified to work during beta testing. See http://www.openpkg.org/showcase.html -- [EMAIL PROTECTED], Cable & Wireless ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
