Don and I were experimenting at the same time, and he had,
| LOCKTIMEOUT=1
| TIMEOUT=1
| SUSPEND=1
Thanks for the testing, Don. I didn't set TIMEOUT; I did try LOCKSLEEP, but
only LOCKTIMEOUT and SUSPEND made a difference.
| :0:LOCKFILE
| { }
| procmail: Extraneous locallockfile ignored
My first thought was to set the lockfile that way, since when I'd be using
this I'd already have a regional lockfile in effect and wouldn't want to
lose it. Given that it is officially "ignored" I'm surprised it still was
forced and took.
I did it this way:
:0:.lock # that was the name I used
$DEFAULT
because I was dropping to $DEFAULT anyway.
I suppose one could do this:
:0c:.lock
{ HOST }
but I'm guessing that cloning procmail is no savings over forking rm; better
to do it as Don did and put up with both the "extraneous local lockfile
ignored" and "forcing lock" error messages.
Come to think of it, I could lose the regional lockfile at that point, do it
this way, and get only the "forcing" warning:
LOCKTIMEOUT=1
SUSPEND=1
LOCKFILE=.lock
LOCKFILE
Unless procmail has some other way besides lockflie removal to get rid of a
file, that is.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail