recent svn.collab.net issues

Now that the svn.collab.net server's been up and running for a couple
of days, is anybody going to look at the issues that plagued it several
days ago?

Just recompiling using an older version of BDB isn't a solution that
is going to do wonders for our stability claims.

On my part, I spent some time working with getting apr/apr-util/httpd
running without core dumps using a bounds checking compiler, which
didn't find any errors with the Subversion part, which is pretty
impressive.

On svn.collab.net, how about setting up a duplicate svn server on a
different port number using the broken setup so that people can do
commits against it to try to get it into a hosed state? Here are
some other ideas:

We could set up a HTTP request mirror (like a switch port mirror) that
could proxy or mirror all HTTP traffic to the main server to the test
repository. Not really sure how this would work on the replies. I
guess the mirroring software would just log the responses.

Or I could write a simple cron script that watches for updates to the
main repository and runs
    svn merge -r HEAD-1:HEAD http://svn.collab.net/repos/svn
on the test repository. A svnadmin dump of the repos would be needed
for this.

It would be great if we could get this problem handled, as several people
have seen it (hint, hint :) )

BTW, has anybody tried running a httpd server under valgrind? The server
could be run that way.

Best,
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