Author: PSE-L(_at_)mail(_dot_)professional(_dot_)org
(Professional Software
Engineering)
Original-Date: Tue, 24 Mar 1998 09:29:44 -0800
Message-ID:
<3(_dot_)0(_dot_)5(_dot_)32(_dot_)19980324092944(_dot_)03a3b3c0(_at_)mail(_dot_)professional(_dot_)org>
:0:$TEMP/FGREPTWITS$LOGEXT
{
INCLUDERC=$PMDIR/spam/notwit.rc
}
The log sez "Extraneous locallockfile ignored", and the recipes are
executed concurrently.
Right.... You can't colon lockfile a { } set
If lockfiling is how one would go about it, what am I doing wrong?
If not, HOW would one limit the execution of multiple copies of the
fgrep recipes? Or do I have to go to each individual recipe and
put locallockfiles on each of them?
I do this as the first line in .procmailrc
LOCKFILE=${HOME}/.procmail.global-procmail.lock
and this as the last line
LOCKFILE
This means I don't have to worry about any local lock files. There's some
disclaimer about when you use the 'c' flag (ie :0c at the start of the
recipe) but I seem to have not run into any problems with it.
You could probably do something similar around the { } recipe if you don't
want to do it globally.
See 'man procmailrc' for more information on the LOCKFILE command
TjL