On May 7, 2005, at 12:03 PM, lists@groundclutter.com wrote:
>
> We think that the problems are the result of having two processes
> trying to do the same copy or move at the same time in the same
> working copy. (FWIW, both the working copy and the repository are
> on a remote fileserver.) It only seems to fail when the copy or
> move involves subdirectories.
Whoa whoa whoa... apples and oranges!
The *repository filesystem* is designed for multiple concurrent
accesses... not the working copy! That's why clients drop
'lockfiles' all over the working copy -- to guarantee that only one
process can ever get write access to an .svn/ area at a time.
If you have multiple processes all trying to edit a working copy at
the same time, I would expect lots of collisions and errors about
'working copy locked', causing client operations to bomb out.
We designed working copies to be shareable by multiple users. (For
example, you and a friend can both take turns running 'svn update'.)
But it's not a place for dozens of concurrent accesses. In that
situation, you should every client process working in a separate
working copy. Working copies are meant to be scratchspaces. Create
lots of them.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat May 7 19:16:26 2005