At 13:36 2001-12-21 -0500, Jed Record wrote:
I have some typical recipies that I have been using and I would like to
get some input on efficiency. When is it appropriate to use a lockfile
Basically, whenver you're writing to a file. Or whenever you're invoking a
process which should really only be running one copy at a time (say, some
sloppy DB update util).
When the determination of a lockfile name is ambiguous (you're not
delivering to a mailbox, but instead to a prog or somesuch, then you'd want
to specify a locallockfile name explicitly. In your examples, they're all
candidates for implicit locking, so long as you provide the ':' flag.
# typical spam marker
:0: H
Please read manpages: ':' flag should be *LAST* flag on line. Anything
which follows it is taken to be the name of the lockfile.
I presume that you're using 'H' here to have the conditions match against
the header. If you read the manpages ('man procmailrc'), you'd find that H
is the default. You'd really only specify it if you wanted to to BODY and
HEADER (if you added B, it'd say BODY only, so to get all, you'd use HB).
[snip]
Most of those subject conditions could be combined into one simple recipe.
# from differs from recieved
Uh, I don't follow the logic - this has the capacity to throw away a LOT of
mail (virtual domains for example).
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail