I removed the race condition by having each parallel ant process using a unique
name. That is really up to the build file, but that is the way it was designed.
So, there shouldn't be any race condition. If 2 files get created at the same
time, each task will remove their own file and do a random b
David,
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,
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 direct
[EMAIL PROTECTED] wrote:
I'm just curious about how usefull other folks would find this.
I've created 2 tasks and .
The use case is where you have parallel ants running (on some server) doing
builds, but 1 part of the build (in our case, some JFCUnit) needs to be single
threaded. By this I mean th
