On 6.4.2007, at 20.36, Timo Sirainen wrote:
I guess this has something to do with NFS attribute caching then.
For now you could disable the check by changing
mbox_sync_file_is_ext_modified() to just contain "return FALSE;" in
mbox-sync.c.
Hmm. Wonder if I should add a new setting for this
On 6.4.2007, at 20.08, Jeff A. Earickson wrote:
But what do you mean duplicated the messages? Same messages exist
multiple times in the mbox file? The only reason I can think of
how that could happen is if you expunged a lot of data from the
middle of the mbox, and then in the middle of the
On Fri, 6 Apr 2007, Timo Sirainen wrote:
Date: Fri, 6 Apr 2007 19:50:07 +0300
From: Timo Sirainen <[EMAIL PROTECTED]>
Reply-To: Dovecot Mailing List
To: Jeff A. Earickson <[EMAIL PROTECTED]>
Cc: dovecot@dovecot.org
Subject: Re: [Dovecot] mbox sync/lock issue, rc28 and later
On
On 6.4.2007, at 15.59, Jeff A. Earickson wrote:
Apr 6 07:22:52 karst dovecot: [ID 107833 mail.error] IMAP
(jaearick): mbox file /var/mail/j/jaearick was modified while we
were syncing, check your locking settings
Pine coughed up an internal error, no core dump, and dovecot
basically doubled
Help!
I just noticed this error this morning, we have been getting a
lot of these in rc28 and rc29, not in rc27 or before:
Apr 6 07:22:52 karst dovecot: [ID 107833 mail.error] IMAP(jaearick): mbox file
/var/mail/j/jaearick was modified while we were syncing, check your locking
settings
Pine
