Bill Moseley asked about using a lockfile on a nexting block
At 12:41 PM 10/12/97 -0500, David W. Tamkin wrote:
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*.
Then commented:
... 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.
I tried it without the "w" and I ended up in a dead-lock situation and I
had to manually remove the lockfile.
Basically, in my .procmailrc I have:
:0c:file.lockfile
{
"file" must not be modified while in here
}
:0:file.lockfile
{
append something to "file"
}
Can someone explain why the "w" is important -- and what exactly it is
waiting for?
Thanks,
Bill Moseley
mailto:moseley(_at_)netcom(_dot_)com