--On Wednesday, December 18, 2002 4:32 PM +1100 Rob Mueller
<[EMAIL PROTECTED]> wrote:
Given that it's for the deliver.db, which is used for duplicate delivery
suppression and sieve, will an aborted locker result in sieve not
correctly processing an email?
I don't think so. Since Sieve always u
> This should be due to internal deadlocks in the berkeley db code. (This
can
> happen when two different processes are trying to upgrade read locks to
> write locks or split a page.) Generally the bigger the database is the
less
> likely this is to happen, which is why you might see it only on yo
--On Wednesday, December 18, 2002 12:39 PM +1100 Rob Mueller
<[EMAIL PROTECTED]> wrote:
I'm just wondering if anyone know what this might be about. Seems to be a
BDB issue and it only happens a few times a day, but I don't know if it's
harmless or not. Interestingly it occurs on our less loaded s
