On 5.1.2007, at 21.47, Bill Cole wrote:
- Added dotlock_use_excl setting. If enabled, dotlocks are created directly using O_EXCL flag, instead of by creating a temporary
file which is hardlinked. O_EXCL is faster, but may not work with NFS.Can you expand on this?
The problem with HFS+ is that it implements hard links some weird way
(http://www.dovecot.org/list/dovecot/2006-August/015287.html). I also
noticed that besides having a bad performance, I ended up in a
situation like this:
~/Maildir$ ls dovecot-uidlist.lock dovecot-uidlist.lock ~/Maildir$ ls |grep dovecot-uidlist.lock ~/Maildir$ /bin/rm dovecot-uidlist.lock rm: dovecot-uidlist.lock: No such file or directory
This made the maildir stuck forever until I just went and deleted the
whole ~/Maildir.
I have been running Dovecot on a MacOS 10.4 PPC machine with
Maildir on local (HFS+) disk for some time and have had
intermittent and hard-to-characterize problems that manifest
themselves as clients (Eudora, Palm VersaMail, and Outlook) timing
out and hanging as one tries to move messages between mailboxes in
the same account. The cargo-cult approach I've used to eliminate
the hangs has been unsatisfying (cycle all clients and Dovecot,
remove index files and temp files in mailbox directories) but even
with rawlogging I have been unable to nail down the source of the
trouble definitively. It looks like maybe bad index files or maybe
some sort of locking issue, but the logs don't show anything other
than the clients timing out and dropping connections.
You should see at least some "lock timeout" errors in logs if it's
because of them.
I don't understand the description of those rc16 changes because it
seems like dotlocking would be irrelevant for Maildir anyway.
Should I set dotlock_use_excl=yes even though I'm using fcntl?
Dotlocking is always used for some things. See if it helps for your
problems :)