Re: [Sks-devel] DB_INIT_LOCK problems?

[Jason Harris]

On Fri, Jul 23, 2004 at 06:15:25PM -0400, Yaron Minsky wrote:
> On Fri, 23 Jul 2004 15:55:26 -0400, Jason Harris <address@hidden> wrote:
> > 
> > Has anyone tried enabling DB_INIT_LOCK with SKS?  I notice it is
> > commented out in the 1.0.7 release and assume it caused problems
> > (or at least confusion) in the past.
> 
> I was never able to get it to work quite properly.  When I enable it
> with a recent version of SKS, everything locks up, though I don't
> remember the details.  I suspect this is because I'm doing something
> wrong with the way I deal with Berkeley DB.  But I've never been able
> to suss it out.

I've enabled it and am running "db[42]_deadlock -t 1.0" from/on the
KDB database directory/environment.  Starting db_deadlock before either
sks process starts has kept my SKS processes running without problems/
complaints for over 4 hours now.

Some Perl code that reads the key db while SKS is running has gotten
DB_LOCK_DEADLOCK/EAGAIN/35 on some $cursor->c_get() calls, but trying
the operation again after a small sleep() works fine.  (Note that I
haven't checked the OCAML code/libraries for this behavior, however.)

This is with BDB 4.2.52.

(I'm pretty sure you'll want to remove Dbenv.RECOVER/DB_RECOVER if you
point two "sks db" or other processes at the same database environment
for testing, too.)

-- 
Jason Harris           |  NIC:  JH329, PGP:  This _is_ PGP-signed, isn't it?
address@hidden _|_ web:  http://keyserver.kjsl.com/~jharris/
          Got photons?   (TM), (C) 2004

pgpqyX1C986wP.pgp
Description: PGP signature