On Tue, Oct 12, 2004 at 03:17:07PM +0200, Samuel Calan wrote:
> We use Subversion in our company and and I attached the whole software.
>
> Now, I have a problem:
>
> I configured WebSVN, so that we have a graphical interface for the
> repositories.
>
> If I commit a large transaktion of files, and in this time I refresh the
> WebBrowser in that WebSVN is called, I get a corrupt repository.
> I will requested to recover the database.
> Now in our company we're 150 persons. So it's very much possible, that this
> conflict can occur!
>
> I have inspected that WebSVN use the "svnlook" command. I have read that
> svnlook is a "read-only"-tool. But if I change the permissions in the
> repository-path "rep/db" to read and execute, WebSVN cannot be executed
> anymore, until I change the permissions to read, write and execute!
>
> My investigation is so: While a commit modify the "rep/db/" directory-path,
> svnlook tries also to modify this directory and a conflict and settlement
> occurs...
>
> I hope you can help me and write me soon, so that I could know, if
> subversion is the right software for our company!
It's read only in that it doesn't modify the contents of the repo.
You're using the BDB backend. Transactions are built in BDB to answer
queries which require write access to the database. So yes you need
write access.
Your probablem with a "corrupt" repository sounds like a permissions
issue. Very likely log files are being created by a different user for
the WebSVN accesses that the server that is servering the svn client
can't read/write to. As a result you get an error.
See: http://svnbook.red-bean.com/svnbook-1.0/ch06s05.html
--
Ben Reser <ben@reser.org>
http://ben.reser.org
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 13 19:31:04 2004