Eric asked,
if you are going to use the brute force / bloody ignorance solution (my
favorite), I actually need to lock on the recipient of the message.
Then fine: LOCKFILE=$HOME/.globalprocmaillock
The problem is that you said earlier that keeping a procmail process
doing nothing while it waits for another to release a lock won't help
with your situation; you said you needed to keep the additional procmail
processes from being forked at all until the system is ready to handle them.
Letting procmail get started and then holding it in place to get a
lockfile won't help.
think we can do this with an array of global locks?
Only if the locks can keep procmail from being invoked at all, because
that's what you said you need.
____________________________________________________________
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