ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Phil Weighill-Smith <>
Subject Re: mutex tasks
Date Thu, 29 Jul 2004 12:16:30 GMT

You're far better (from the atomicity and portability points-of-view)
creating a directory instead of a file - directories can't be re-created
on any filesystem I've used while files can be (so you might think you
created the lock file but didn't due to a race condition).

Phil :n.

On Thu, 2004-07-29 at 13:11, wrote:

> I've just dome some testing in XP. The locks are simply zero length files and
> nothing more. Also, because of the random backoff approach, I think it would be
> pretty robust. To clean up any locks left over from previous attempts, a
> mastster scheduler could simply remove all files in the locks directory. Should
> I post code, and a build file example? I could also submit a patch to bugzilla
> with all the stuff attached.
> David
> Quoting Steve Loughran <>:
> > 
> > This is interesting. File locks worry me as they can be quirky on 
> > platforms and across shared file systems. And on winnt workstation, 
> > locks never seem to get released when an app crashes (unlike winnt server).
> > 
> > What have you tested on?
> > 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Phil Weighill-Smith <>
Volantis Systems

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message