Bill Moseley asked,
| What I'd like to do is place the entire block above (except the global
| LOCKFILE) within a locked nesting block that uses the SAME lock file as
| used later in the procmail recipe?
|
| :0c:summary.spam$LOCKEXT
| {
| ...
| }
|
| But era pointed [out]:
|
| >$ cat scratch/rc
| > :0:pluck
| > {
| > :0:
| > /tmp/output
| > }
| >
| > $ procmail DEFAULT=/dev/null scratch/rc </dev/null
| > procmail: Extraneous locallockfile ignored
Different situation; a nesting block that does not launch a clone cannot
take a local lockfile on the recipe that starts the braces. A nesting block
that does launch a clone *can*.
| So how do I clone and preserve the lock file. If I clone within the
| LOCKFILE block above, won't the parent remove the LOCKFILE when it jumps
| across the current nesting level?
No, it should remove it when the clone exits. I feel more comfortable adding
the `w' or `W' flag to the recipe that creates the clone (I've never dared
to try it without `w'), but that may be unnecessary.