On Feb 10, 2015, at 9:46 PM, Ken Hornstein <[email protected]> wrote: > Thanks, yeah, that is wrong. Me (or someone else) will apply this fix, > and the others. I don't think many people use local spool files combined > with dot locking, so this code path doesn't get much love.
But I have to ask why someone would want to run things this way. BSD systems - by definition - use flock() in /var/mail. If you run MH with dot locking for /var/mail, you're eventually going to lose mail, since the MDA will still use flock(), even if you don't. Not to mention other tools in ports that will be assuming flock() for /var/mail. This is why the incoming mail spool gets its own locking treatment, distinct from everything else. I would prefer to see a much stronger use case made for this before accepting it into the code base.
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Nmh-workers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/nmh-workers
