Re: svn stability problems

Blair Zajac wrote:

Branko ?ibej wrote:
  

Gustavo Niemeyer wrote:

I'm surprised to see you reporting a bad experience, as we have a very
good experience with subversion/db stability. We had many problems with
our previous server (disk failure, out of memory, out of disk, power
problems, etc), and a simple db_recover always solved our problems.

I'm beginning to get a nagging suspicion. It seems to me that everyone
who reported stability problems /also/ repotred problems when trying to
configure Apache authorization to control access to parts of the
repository, rahter than to whole repositories. The two may well be
connected, because those Apache authz configs I've seen posted to the
list all ignore the fact that the public URLs are /not/ where the
changes are made. Is it possible that this confuses Apache (or rather,
mod_dav_svn) so much that it does stupid things to the repo?
    

Not for me at least. I protect the whole repository. I do however
have an HTML and an XML method of browsing the repository.

Hm. That really shouldn't be a problem, I have almost exactly the same
setup myself, with no problems as yet. (And still running 0.14.2,
because I haven't had time to upgrade yet...)

-- 
Brane Čibej   brane_at_xbc.nu   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org