On Fri, Sep 29, 2006 at 12:00:13AM +0200, Eric Y. Kow wrote:
> Could somebody with experience writing procmail recipes please review
> this patch for me?
>
> {
> hunk ./best_practices.tex 413
> -:0:
> +:0
> hunk ./darcs.lhs 542
> -:0:
> +:0
> }
The trailing colon requests that access to the target is
protected with a lockfile. I don't have the source in front of
my eyes now, but I think these procmail examples pipe the mail
to darcs, so without a lockfile, two simultaneously arriving
mails would start two simultaneously running darcs processes,
and if both of them want to "darcs lock" the same repo, the
second one will hang for a while, printing a lot of "Cant get
lock" messages. But on the other hand, a procmail lock will time
out after 17 minutes and execute the (second) pipe anyway, and
if they access different repos there's no need for one to wait
for the other. I think we should trust darcs to cope with this
and omit the procmail locking.
--
Tommy Pettersson <[EMAIL PROTECTED]>
_______________________________________________
darcs-devel mailing list
[email protected]
http://www.abridgegame.org/cgi-bin/mailman/listinfo/darcs-devel
