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

Miller, Eric wrote:
> 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.

Both file:// and svn+ssh:// use file locking, so you /shouldn't/ have
issues, except if the repository is located on a remotely mounted
filesystem without an effective filesystem lock. Specifically, there
are some NFS implementations which don't have very good lock support (or
people turn off lockd because it makes everything "slower"). :(

The performance issue of always having to start up an svnserve session
for each connection (on top of starting up an SSH connection), means
that svn+ssh:// cannot be considered a high performance method. But it
can be configured as a very high security system, ala:

        http://subversion.tigris.org/faq.html#ssh-svnserve-location
        http://svn.collab.net/repos/svn/trunk/notes/ssh-tricks

YMMV

John

---------------------------------------------------------------------
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:51:15 CET