Ryan Schmidt wrote:
> Try verifying your repository with "svnadmin verify" to see if it's
> alright. "svnadmin recover" if necessary.
>
> If you're using a BDB repository, consider switching to FSFS. I don't
> think it's necessarily WebSVN that's causing the problem, but possibly
> just any concurrent access from another process, possibly over a
> different protocol. FSFS doesn't have problems with that; I believe BDB
> does. See the FAQ for how to convert.
>
> Please consider upgrading your Apache. 2.0.50 is almost two years old.
>
>
>
>
Sorry, I forgot to write that I use FSFS for all repositories. I already
considered the concurrent access by websvn to be the problem. So I did a
"svn cat ..." of a repository file on the server as it is the same thing
websvn does when displaying a file doesn't it? This didn't cause any
problems.
So after all apache is the most probable source of the problem? I'll
consider an update then but I wanted to make sure it is really neccessary.
Markus
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 24 13:57:55 2006