[EMAIL PROTECTED] writes:
> I've also started getting this. When I do multiple upgrades I can have
> almost a whole screen full of this same message.
> This is not a question of waiting and re-trying, there is definitely
> something wrong. This only started happening in the last two days ....
>
>
>
>
[...]
>
>
> Also sprach Steven Hatfield :
> >
> > Hi all,
> > 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...
> This happens when two rpm process try to access simultaneously the rpm
> database. In fact, even if they are sequential, unlocking the base can
> takes sufficient time for the second access to be rejected. Just wait a
> bit and re-try.
This behaviour is fixed in rpm 3.0.5-23mdk: rpm waits for the lock to release
without issuing any warning.
--
Fred - May the source be with you
