[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] dot locking broken?
From: |
Lyndon Nerenberg |
Subject: |
Re: [Nmh-workers] dot locking broken? |
Date: |
Wed, 11 Feb 2015 18:00:58 -0800 |
On Feb 10, 2015, at 9:46 PM, Ken Hornstein <address@hidden> 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
Re: [Nmh-workers] dot locking broken?, Marcin Cieslak, 2015/02/13