[Dovecot] locking strategies?

[Joe Allesi -X (joallesi - Coyote Creek Consulting at Cisco)]

You had to ask that...we're still on 0.99, but we're testing other
options as well. We're pretty restricted to RHEL 4.x, but with the help
of others on the list we've made some progress with testing 1.0.7 on 4.x
as well. We have some clients using a java based IMAP application with
some major issues, so we're moving slow on changing our config for one
bad application. We've seen this issue and others, and Red Hat says
they're recommending dotlock to increase stability of the mboxes for the
short-term:

-> fcntl() failed with mbox file /var/mail/XXX: Resource deadlock
avoided
-> file istream.c: line 93 (i_stream_set_read_limit): assertion failed:
(stream->v_size == 0 || v_offset <= stream->v_size)
-> Corrupted modify log file
/users/XXX/mail/.imap/INBOX/.imap.index.log.2: Contains more data than
expected
-> Error rewriting mbox file /users/XXX/mail/Folder Name: Unexpected end
of file



-----Original Message-----
From: dovecot-bounces+joallesi=cisco.com at dovecot.org
[mailto:dovecot-bounces+joallesi=cisco.com at dovecot.org] On Behalf Of
Charles Marcus
Sent: Friday, November 30, 2007 6:34 PM
To: Dovecot Mailing List
Subject: Re: [Dovecot] locking strategies?

On 11/30/2007 Joe Allesi -X (joallesi - Coyote Creek Consulting at
Cisco) wrote:
> Any known issues with these locking strategies? (RHEL 4.x default)

Which version of dovecot?