Bug#253138: bogofilter: error when processing concurrently from procmail
Matthias Andree
matthias.andree at gmx.de
Mon Jun 7 15:34:23 CEST 2004
On Mon, 07 Jun 2004, Clint Adams wrote:
> Thinko somewhere?
Possibly in datastore.c:ds_open().
When a data base can't be opened for write, it tries to create it no
matter what the cause for failure was - which might have been EAGAIN for
lock contention, which is the likely cause here. Locking failures
however should be propagated up to the caller who can then bail out or
retry. Unfortunately, the db_open interface returns the handle which may
be NULL to indicate a problem, but has no means to propagate the error
code back. Maybe it should return (void *)-1 to specify "retry".
I don't have time to code this now however.
--
Matthias Andree
Encrypted mail welcome: my GnuPG key ID is 0x052E7D95
More information about the bogofilter-dev
mailing list