On Jul 5, 2005, at 7:42 AM, Christoph Bartoschek wrote:
>
> In our case the only way to access the database is with svn://
> because all
> other protocols are disabled. svnlook and svnadmin are only used when
> svnserve is stopped. Therefore developers use always the same
> svnserve
> daemon. Given this scenario: when two developers access svnserve at
> nearly
> the same time. Are the libsvn_fs accesses still independent?
Yes.
You can have N svnserve 'child' processes all serving different
clients at the same time. And they're still considered equal peers
when it comes to accessing the database. There's nothing wrong with
concurrent database access; what's wrong is that one svnserve
process can crash, wedge the repository, and the other N-1 svnserve
processes will either hang or be unable to do anything. Nothing
notices/fixes the wedge other than a human. This is why we need
either an 'svnd' akin to mysqld, or BDB needs to learn to auto-
recover itself.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 5 14:55:44 2005