Am Dienstag 05 Juli 2005 14:31 schrieb Ben Collins-Sussman:
> svnserve is acting as a *network* gateway, perhaps... but there's
> nothing preventing some other program linked to libsvn_fs from
> accessing the repository as well. For example, you might have a hook-
> script that runs 'svnlook'. Or a user with a shell on the system
> might run 'svn checkout file:///'.
>
> The point is that there's no ueber-process guarding the health of the
> tables themselves. Instead, there's a bunch of libsvn_fs processes
> potentially all accessing the repository at once -- svnserve,
> mod_dav_svn, svn, svnlook, svnadmin -- all equal peers, all unaware
> of each other. Any one of these programs could wedge the database,
> and none of the programs knows how to detect this and un-wedge.
>
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?
Christoph
---------------------------------------------------------------------
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:49:15 2005