[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Subversion/BerkeleyDB lock problem (part II)

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2004-07-12 08:13:01 CEST

--On Sunday, July 11, 2004 10:21 PM +0200 Morten Mertner <morten@mertner.com>

> Like I said in my last report, this is a real show-stopper. Having to reboot
> the server
> to keep the repository alive is just, well, you know.

Unless there is a kernel problem related to shared memory (possible with
2.6.7, but I don't know), you shouldn't have to reboot. The one thing I'd
suggest doing is trying to compile bdb with debugging symbols enabled (i.e.
only '-g' and no '-O2') and try to get a backtrace of where svnadmin hangs.
-- justin

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 12 08:13:27 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.