On Mon, 26 Oct 1998 21:27:06 -0800 (PST), Nick Halloway
<snowe(_at_)rain(_dot_)org> wrote:
Does the lockfile that is defined at the beginning of the .procmailrc
Um, you mean like this?
LOCKFILE=somefile
This is not necessarily a good idea. It prevents +other+ Procmails
from running until this instance has finished (that is, other copies
of Procmail using the same .procmailrc, and of course, any other
programs you may have that pay attention to the lock file you've
chosen [usually none, but there's a potential to use this for
communicating with other programs]).
stop the .procmailrc from being run again until all the pipes called
by the first one have finished?
Perhaps this is really what you want then. The rest of your question
seems a little unrelated to this, though. Can you give a specific
example of what you want to accomplish?
Or when it's piped a mail message to a script, does procmail then
quit and release its lockfile?
Normally, yes, unless you have been using an :f flag or a :c flag or
something on the recipe in question. In other words, if it's a
delivering recipe and you haven't specifically asked Procmail to
continue after completing it, this is what happens.
If you mean, does Procmail quit immediately when the script in
question has read the message, see below.
I want the .procmailrc to not quit when it's piped a message to a
script, until the script ends. How can this be done?
Use the :w flag on the recipe in question.
Hope this helps,
/* era */
--
Bot Bait: It shouldn't even matter whether (`') Just (`') http://www.iki
I am a resident of the State of Washington \/ Married! \/ .fi/~era/