Hi On Wed, 2003-09-10 at 14:11, [EMAIL PROTECTED] wrote: > This is a resend, I didn't recieve the message myself. > ------------- > > I'm trying to use openpkg as a local user on a Solaris system. This is > what I've done: > > Installed the current version with the command: > sh openpkg-20030909-20030909.src.sh > --prefix=/ebar/efs1/home1/s01/s011269/openpkg/local/ > > This seems to work like a charm. > > Then I run the resulting .sh-file: > sh openpkg-20030909-20030909.sparc64-solaris9-eeh.sh > > And get this: > openpkg-20030909-20030909.sparc64-solaris9-eeh.sh: installing into > /ebar/efs1/home1/s01/s011269/openpkg/local... > openpkg:WARNING: skipping addition of > /ebar/efs1/home1/s01/s011269/openpkg/local/lib/openpkg/bash to > /etc/shells > openpkg:WARNING: (would require root-privileges) > openpkg:WARNING: skipping creation of system run-command hooks > openpkg:WARNING: (would require root-privileges) > openpkg:WARNING: skipping creation of system cron hooks > openpkg:WARNING: (would require root-privileges) > openpkg-20030909-20030909.sparc64-solaris9-eeh.sh: installation done. > > ... Not sure how bad that is... Probably is, come to think of it...
Looks normal for a non-root install. No harm done, except that servers won't be restarted on reboot, and cron jobs that rotate logs won't get run. Does anybody have ideas how to have user servers restarted? The cron jobs for log rotation is the easy part > > Anyway, optimistic as I am, I proceed. At first with mozilla, but that > didn't really work, then with antiword, but I got the same errors... > Something about rpm-tools... > > So I obviously try to install openpkg-tool, but from rpmbuild get this: > $ rpmbuild openpkg-tool.spec > 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 > /ebar/efs1/home1/s01/s011269/openpkg/local/RPM/DB Some suggestions (sorry if it sounds obvious :-) 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). 5. Make sure the right version of rpm gets called by your command. HTH! Conrad > > ... And now I'm stranded. Any suggestions? -- ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
