Yeah, I've noticed that using fsfs seems to make the difference. I converted my other project to fsfs with svnadmin dump & load, and now its faster to retrieve things and it doesn't die. Not to mention that websvn no longer needs write access to the repo just to display its contents :)
SVN is great :) The way it does branches especially. --- James On 05/11/2005, at 11:26 PM, Norman Rasmussen wrote: > I've been using SVN for all my personal projects, and it's great. I > use it via ssh+svn, and the db is the new FSFS format. > > On 10/29/05, Lars T. Mikkelsen <[EMAIL PROTECTED]> wrote: >> On Sat, Oct 29, 2005 at 06:53:04PM +1000, James Bunton wrote: >>> Unfortunately I've not had good experiences with SVN lately. Used it >>> in >>> a school project. It was possibly just me not setting it up >>> correctly, >>> but it broke itself regularly. I had to run svnadmin recover way too >>> many times for comfort. >> >> Subversion has been very stable since at least 1.0. The issues you are >> experiencing could be due to the fact that the Berkely DB repository >> data-store is not usable on network shares (e.g. NFS) - it *will* >> corrupt the repository. Subversion 1.1 introduced a new filesystem >> repository data-store (FSFS) which is more stable and usable on >> network >> shares. FSFS also became the default data-store in 1.2. >> >> Best regards, >> Lars >> _______________________________________________ >> py-transports mailing list >> py-transports@blathersource.org >> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports >> > > > -- > - Norman Rasmussen > - Email: [EMAIL PROTECTED] > - Home page: http://norman.rasmussen.co.za/ > _______________________________________________ > py-transports mailing list > py-transports@blathersource.org > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports >
