On Sunday 17 October 2004 18:33, Jay Cornwall wrote:
> John Szakmeister wrote:
> > What version of BDB are you using? 4.1.x is known to have a shared
> > memory bug, that Subversion brings out in full color, especially on
> > machines with multiple processors. You should be using the latest
> > stable version, 4.2.52.
>
> I'm using BDB 4.2.52, as mentioned in my first post. The server is
> running on RedHat Enterprise Linux 3.0 ES which comes with BDB 4.1.x by
> default; I ensure Subversion uses the correct DB library (installed
> into /usr/local/db) on compilation, and I've checked that it (and
> Apache) link to the correct version with ldd.
>
> If it's possible I missed something else which might have to link to
> BDB 4.2, maybe that's the problem?
We upgraded to RHEL 3.0 ES about 6 months ago, and have experienced no
problems. Just to double check things, I would do an ldd on svn,
svnadmin, svnlook, httpd, and mod_dav_svn.so. All of them should have
db-4.2 listed and no other versions. If you see both db-4.1 and db-4.2,
then you've got a problem. Also, if you haven't done so, there are a
couple of patches on Sleepycat's webpage. You might want to apply those
to db-4.2.52.
And yes, if one of those isn't correctly linked to right DB library, you
can cause yourself some headaches, and potentially corrupt the
repository.
Also, getting the permissions right is difficult, especially when you
throw in file access. When you've found your repository horked, have you
ever noticed if the permissions where off? In my testing, I've found
that strange things can happen if the permissions were off, but I've
never seen the errors that you have. Is there some reason you need file
access? I've found that restricting access to just one method really
helps to avoid problems.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 18 01:59:00 2004