Evgeny Kotkov <evgeny.kot...@visualsvn.com> writes: >> Evgeny Kotkov <evgeny.kot...@visualsvn.com> writes: >> >>> The reason why this error is propagated up the stack is that we only examine >>> the 'ignore_enoent' argument after the first apr_file_remove() call. This >>> is >>> racy — if we get a EACCES during the first attempt to remove a file, and the >>> file is simultaneously removed from the disk, the next attempt to remove it >>> would fail with a ENOENT, even with 'ignore_enoent'. I think we should >>> fix this by suppressing ENOENTs from every apr_file_remove() call, not >>> just the first one. >> >> Sounds plausible. > > Here is the patch for this part of the issue. Log message:
I have already committed something, but feel free to commit an additional change if you think it better. -- Philip Martin | Subversion Committer WANdisco // *Non-Stop Data*
