On Thu, Aug 23, 2012 at 01:49:07PM -0500, Derek Martin wrote: > > Not really. You can't really fix this. If mutt can't lock the folder > then other processes (e.g. the MDA) can change the contents out from > under Mutt while it's reading the file, potentially resulting in an > inconsistent state.
Actually the MTA just appends to the file. It can get messy when a second mutt or so with write access changes the mbox more arbitrarily. > > But, there's probably not really any good reason to read mail from a > read-only NFS mount, so just stop doing that, and your problem should > go away. The main reason is to see non-text without IO-redirection. Readonly because I liked to try with least possible privileges. > - Dot-locking is (or at least was, and may still be) unreliable over NFS > - POSIX locking (i.e. fctnl()) is not. I know. From reading the source, I am more puzzled what is really happening. The mx_lock_file function tries fcntl first, and only if this fails tries dotlocking. fcntl()-locking works at least once upon startup. I'll do more debugging to get more insight into this. Bye, Joerg
signature.asc
Description: Digital signature
