On Fri, 10 May 2002, Andrew Edelstein wrote:
More correctily, when a the conditions contained in a :0: recipe match and the
action is to be carried out, procmail will wait until the lock is removed.[1]
The lock may have been created by a program other than procmail, such as a
shell or perl script run out of cron.
Hi,
thank you very much ... so using the :0: option makes setting the
$LOCKFILE in the procmailrc redundant?
For example:
:0:
* ^TOprocmail
procmail
so the verbose shows me:
procmail: Locking "procmail.lock"
procmail: Assigning "LASTFOLDER=procmail"
procmail: Opening "procmail"
procmail: Acquiring kernel-lock
procmail: Unlocking "procmail.lock"
So what is the LOCKFILE setting in procmailrc good for?
For example:
LOCKFILE=$HOME/.lockmail
with verbose:
procmail: Unlocking "/home/olifuc/Mail/.lockmail"
Oliver
--
... don't touch the bang-bang fruit ...
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail