Re: [Sks-devel] DB_INIT_LOCK problems?

[Yaron Minsky]

On Sun, 25 Jul 2004 23:33:56 -0400, Jason Harris <address@hidden> wrote:
> On Sun, Jul 25, 2004 at 09:44:40PM -0400, Yaron Minsky wrote:
> 
> It seems like SKS is locking up in a different way now (TZ=UTC):
> 
> 2004-07-26 02:01:42 0 keys found
> 2004-07-26 02:45:11 Checkpointing database
> 2004-07-26 02:45:26 Checkpointing complete
> 2004-07-26 03:00:00 Calculating DB stats
> 
> "sks db" remains responsive but "sks recon" stopped logging events
> at 02:01:32 without reporting any errors.  Only a "kill -9" worked
> to kill the recon process.

Yeah, that's more like the behavior I've seen when playing with this. 
Is the difference whether or not you told it to compute DB stats
initially?

> As for being single-threaded, if any signal handlers interrupt any
> database operations in progress and attempt to do any new database
> operations, they could cause deadlock.

The only signal I really use is SIGALARM, and that's just for waking
up (and aborting) long-running transactions.  In any case, the 
behavior you shows doesn't involve any interrupts, since interrupts
announce themselves on the log.