Branko ?ibej wrote:
Brandon Ehle wrote:
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?
We're not doing anything of the sort here and having lots of problems,
but I did notice that the people having trouble (Me, Blair, David) are
all running a version of RedHat of some sort. Gustavo which OS / distro
is hosting your server?
Interesting. Are you all using RedHats db-4.x package? Did RedHat screw
up it's Berkeley DB RPMs? Or maybe its kernel locking primitives? Ah,
lots of interesting questions here...
I'm using my own compiled db 4.1.25 with my own compiled gcc 3.2.1.
Blair
--
Blair Zajac blair@orcaware.com
Plots of your system's performance - http://www.orcaware.com/orca/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:06:49 2006