Branko Čibej wrote:
> Nonsense. Any system component may touch the files I create only in a
> way that doesn't interfere with normal file handling semantics. I submit
> that any filter drivers that are fiddling with those files are broken if
> my user-mod app can detect them (via an access-denied status on move,
> for example).
Yes, this is the one big clue (it seems to me) that NTFS may be at
fault...access denied is the return code, not sharing violation. I can
only make access denied errors occur if the destination file is
read-only or if I don't have permissions to one of the files. Sharing
violation is the normal return code for 'something else is dorking with
the file' type situations. Perhaps filter drivers can screw with that,
though, I don't know...
Anyway, immediately after getting a failure I can go look at the files
-- the destination file is not read-only and I have full permissions on
both. AND a simple retry works.
DJ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 23 03:18:21 2003