On 9 Apr, David W. Tamkin wrote:
|| I can't think of a way to test this on my own ...
|
| Yes, I can. A verbose logfile will say whether procmail is trying to get a
| lock. Nevermind.
But I can't nevermind. This stuff is fun. ;-)
$ touch bar
$ cat thisrc
DEFAULT = /dev/null
LOGABSTRACT = no
foo = bar
:0
* ! ? test -d $DEFAULT
{ locallock=: }
LOG="before recipe:
`ls -l $foo*`
"
LOG="during recipe:
"
:0 wi$locallock$foo$LOCKEXT
|ls -l bar* 1>&2
$ procmail ./thisrc </dev/null
before recipe:
-rw------- 1 deh users 0 Apr 9 16:32 bar
during recipe:
-rw------- 1 deh users 0 Apr 9 16:32 bar
-r-------- 1 deh users 1 Apr 9 16:35 bar.lock
--
Reply to list please, or append "6" to "procmail" in address if you must.
Spammers' unrelenting address harvesting forces me to this...reluctantly.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail