RE: Re: svn not atomic with file:/// access?

 
> Like any multi-user database, you need a server such as svnserve or
> Apache to safely mediate concurrent access. As Les implies,
> Subversion may try to use file locking in this situation (sorry, I
> can't say for certain), but this leaves you dependent on the correct
> functioning of locking in your particular OS/filesystem layers.

I don't want to hijack this thread, but can svn+ssh:// have the same
issues? Since svn+ssh:// fires up a new svnserve process for each
repository access session there is no "central" server to handle
concurrency issues.

If so, this would explain a lot of the intermittent failures we've been
seeing with svn+ssh://.

Eric

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-26 18:23:11 CET