# from David Golden
# on Wednesday 14 January 2009 04:49:
>Without really understanding the details,
>my wild guess is that calling "unlink" schedules a file for deletion
> and there is a lag before it executes and subsequent checks for
> deletion sometimes fail. I've been able to make the problems "go
> away" by sleeping a couple seconds before checking that files are
> removed. But that's a hack, not a real fix.
I don't think there is a 'real fix' for much to do with the filesystem
on windows. I've seen "while(1) {unlink($file) and last}" (or roughly
that) as a workaround (possibly even in M::B test code.)
--Eric
--
Office: (503) 643-1684
Mobile: (503) 880-4750
http://scratchcomputing.com
