I don't understand the logic to seeing a screen full of "cannot get shared
lock" messages everytime you do an upgrade of multiple packages. Does the
user need to see this for instance while upgrading several KDE packages via
"rpm -Uvh kde*" ? What purpose would this serve ?
Vincent Danen
<vdanen@mandrakesoft. To: [EMAIL PROTECTED]
com> cc:
Sent by: Subject: Re: [Cooker] RPM spewing
"cannot get shared lock on
cooker-owner@linux-ma database"
ndrake.com
10/04/2000 09:21 AM
Please respond to
cooker
On Wed Oct 04, 2000 at 11:04:44AM -0400, Steven Hatfield wrote:
> I'm having a problem trying to update my Cooker box with the newest RPMS.
> I've mirrored the cooker RPMS directory, and am doing "rpm -Fvh *.rpm"
and
> it's working - with the exception of sending the message "cannot get
shared
> lock on database" while displaying the "#"s. To verify, I'm running this
as
> root on a box that seems to be working just fine...
>
> What can be wrong?
Nothing is wrong. In fact, I like this better than the old way. For
instance, if I install things selectively (ie. rpm -Fvh X*) and after
the last package it isn't finished but I do another selective freshen,
rpm used to exit saying it couldn't get an exclusive lock on the
database, which meant I had to wait until the cpu dropped and I would
guess as to whether it was finished updating to start the next
freshen. This way it will sit there and keep retrying to get the lock
until it is able to so I don't have to sit there and watch it. The
messages are a little more annoying, but I wouldn't worry about it (I
much prefer the way rpm handles now than how it used to).
--
[EMAIL PROTECTED], OpenPGP key available on www.keyserver.net
// Danen Consulting Services www.danen.net, www.freezer-burn.org
// MandrakeSoft, Inc. www.linux-mandrake.com
1024D/FE6F2AFD 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD
Current Linux uptime: 11 hours 11 minutes.
