On Wed, Sep 10, 2003 at 10:36:10PM -0700, Conrad Steenberg wrote:
[...]
> Some suggestions (sorry if it sounds obvious :-)
Same here.
> 1. Make sure the openpkg rpm db is intact in the above directory
> 2. Make sure some other process isn't holding a lock on the db files
> 3. Check the permissions of the db directory, your user should have
> read and write access to the dir.
> 4. Do an 'strace rpm -q openpkg' and send the output, that should show
> which system call failed (if the problem is in fact a permission or
> locking problem).
There is a strace command under Solaris, but it is probably better to
use "truss".
strace - print STREAMS trace messages
truss - trace system calls and signals
> 5. Make sure the right version of rpm gets called by your command.
That is a good idea, because there may be an /opt/sfw/bin/rpm from the
companion cd.
(mk)
--
Matthias Kurz; Fuldastr. 3; D-28199 Bremen; VOICE +49 421 53 600 47
>> Im pr�motorischen Cortex kann jeder ein Held sein. (bdw) <<
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
