On Fri, Apr 30, 2004 at 08:21:48PM +0300, Timo Sirainen wrote:
On 30.4.2004, at 18:22, Olivier Tharan wrote:
| Apr 30 17:17:32 munster pop3(zzzzzzz): Error indexing mbox file /var/mail/zzzzzzz: LF not found where expected .. A precision: /var/mail is a NFS filesystem (from a Netapp). The indexes are on a local disk.
The same test on a box with a local spool (no NFS) does not trigger the errors. On both machines, this is dovecot-0.99.10.4 from the FreeBSD ports.
mail_read_mmaped = no I guess?
Recently I've began wondering what exactly are NFS client's caching rules. When exactly does it try to read the file from local cache and when does it check that it's not changed in server? Maybe the only answer to write fully NFS compatible code is to read the actual NFS client implementations of most popular OSes :)
Of course, this might not be NFS-related bug at all even though it triggers only with NFS. Anyway, I don't think I'll spend any time wondering about it as mbox code will be rewritten anyway.
Hi Timo,
may I ask for a working stable Maildir-index before you go at the mbox-rewrite? ;-)
I'd just love to get rid of the (few) quierks that my v0.99.8 has. But unfornationally every time I try an update or fetch a cvs copy the index-code seems to be (still?) broken :-(
best regards