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 <[EMAIL PROTECTED]>: > > 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
