RPM locks on Solaris 9 question

["Dennis McRitchie" <dmcr Princeton EDU>]

Hi Jeff,

I saw your post (pasted below) on another forum about how to resolve a
"Resource temporarily unavailable" error and have a couple of related
questions.

I just successfully built and installed rpm 4.2 on Solaris 9 (I gave up on
debugedit though). When I typed in:
$ rpm --initdb

I got:
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)


Then I tried:
$ rpm --rebuilddb

and got:
rpmdb: mmap: Resource temporarily unavailable
error: db4 error(11) from dbenv->open: Resource temporarily unavailable
error: cannot open Packages index

Both before and after these commands, there were no files in /var/lib/rpm.
So I followed your final piece of advice below and created a macros file
with:
%__dbi_cdb create cdb mpool mp_mmapsize=16Mb mp_size=1Mb private

and then retried:
$ rpm --initdb

This time it worked and __db.001 and Packages were created in var/lib/rpm.

My questions are:
1) What are the implications of disabling concurrent access locks, and
re-enabling fcntl(2)
lock on packages? This build of rpm and all related files are on a mounted
file system. If multiple users (mounting this file system from different
machines) were to try to install packages on their local systems at the same
time, would this be a problem?
2) If I were to subsequently upgrade to kernel+NPTL and glibc+NPTL, then
what do I need to do to go back to concurrent access locks? Just remove the
newly created macros file?

Thanks again for your help.

Dennis

Dennis McRitchie
Research & Academic Applications Support (RAAS)
Princeton University

vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
From:  Jeff Johnson <jbj@r...>
Date:  Mon Mar 10, 2003  5:59 pm
Subject:  Re: resource temporarily unavailable error

On Mon, Mar 10, 2003 at 04:49:20PM -0000, Paul Foxton wrote:
> Thanks for your help so far Jeff,
>
> I tried removing the files in question, but the problem remains.
>
> Is my only choice now to take the server down and upgrade the kernel?

Kernel w/o NPTL? Yes, upgrading to kernel+NPTL and glibc+NPTL is recommended
somewhen soon if using rpm-4.2, but meanwhile ...


... the next thing to try is putting in /etc/rpm/macros (create)

%__dbi_cdb create cdb mpool mp_mmapsize=16Mb mp_size=1Mb private

Note "private", disables concurrent access locks, re-enables fcntl(2)
lock on packages with rpm 4.2/4.1.1.