Re: database locking woes part 2

[Ian Peters <itp ximian com>]

More information -- lock-breaker is not able to break the database lock
until version 4.0.3 -- previous versions did not display this behavior. 
Peter Bowen and I are looking at the differences between the 4.0.2 and
4.0.3 trees now to try and find the regression.  Hopefully, once we know
exactly what is broken, we'll be able to come up with a work-around to
keep Red Carpet from accidentally breaking rpm locks.

Ian

On Mon, 2002-07-29 at 17:21, Ian Peters wrote:
> On Mon, 2002-07-29 at 17:08, Jeff Johnson wrote:
> > > # ./lock-breaker
> > > error: cannot get shared lock on /var/lib/rpm/Packages
> > > error: cannot open Packages index using db3 - Operation not permitted (1)
> > > Failed to open rpm database O_RDONLY
> > > Opened rpm database O_RDONLY
> > > 
> > > That second open really should not have succeeded.
> > > 
> > > Am I totally off-base, or missing something obvious here?
> > 
> > Without (yet) looking at the lock-breaker code, I'd guess that an rpmdbOpen()
> > return code is screwed.
> > 
> > Running with strace should show the fcntl errno. If success, then fcntl has
> > weird semantics, if fail, then I've screwed up an rpmdbOpen() return code.
> 
> If it helps, here's a revised version of lock-breaker that actually runs
> a query after it succeeds in opening the database.  This should prove
> that it's not just an error in return codes, that this actually is
> getting a valid database handle.
> 
> Ian
> 
> -- 
> Ian Peters <itp@ximian.com>
> Ximian, Inc.
-- 
Ian Peters <itp@ximian.com>
Ximian, Inc.