On Tue, Mar 08, 2016 at 11:53:03 -0600, Derek Martin wrote: > On Tue, Mar 08, 2016 at 04:39:57PM +0000, Richard Russon wrote: > > > How do you ensure data integrity of, say, an mbox mailstore if you're > > > not locking? > > > > Don't know. > > > > https://github.com/neomutt/neomutt/commit/5adde051f0ae67bfc8aeea0a26060c4e6b0685e4 > > Yeah, looked into this for a minute, and determined it's atrocious. > Should lead to mail store corruption unless you're only using maildir. > The fact that Mutt isn't multithreaded is not interesting; the fact > that multiple processes (e.g. your MDA) may read and write the mail > store files simultaneously IS. Locking is important, and this patch > is misguided.
Reading the manpages, it seems that these are about not using a process-level mutex lock, not file-level locking mechanisms. --Ben
