On Thu, Jun 22, 2006 at 09:25:17AM -0700, Bart Schaefer wrote:
On 6/22/06, Dallman Ross <dman(_at_)nomotek(_dot_)com> wrote:
My question above was specifically as to whether the name for
the lockfile needs to be something other than the file I wish
to write to (plus $LOCKEXT).
As far as procmail goes, the name of the lockfile doesn't make any
difference at all, so long as it isn't a file used for something other
than locking.
Thanks, Bart.
I'll leave your short explanation in one more time, too, as it's
very interesting. Even with all the quoting, we're at less than a
standard screenful, so I think that's okay. -- Dallman
The reason for $LOCKEXT is for procmail to play nicely with the
"maillock" protocol, which is the old file-based /usr/spool/mail
locking scheme use on (IIRC) sysv unix platforms. In that case
the lock file name really does have to be the base file name with
$LOCKEXT added. E.g. you can use LOCKFILE=$DEFAULT$LOCKEXT to
prevent all access to the system mailbox for the current user, on
a platform that supports maillock.
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail