On Jan 17, 2007, at 09:07, Paul Lussier wrote:
This is also how you can fix your subversion repository if you ever get into that bind. Svn originally used a berkleydb back-end and occasionally would suffer from a similar problem.
I'm curious - does anybody know what's up with the BerkeleyDB? It's been around for a long while, and I've seen corruption before, but rarely. It seems to be becoming much more common.
Maybe some key employees left?Maybe more projects have just recently switched to using it for a backend? Maybe the programmers don't use the proper functions to ensure consistency?
Maybe it's just bad luck (mine or Oracle's karma)? -Bill ----- Bill McGonigle, Owner Work: 603.448.4440 BFC Computing, LLC Home: 603.448.1668 [EMAIL PROTECTED] Cell: 603.252.2606 http://www.bfccomputing.com/ Page: 603.442.1833 Blog: http://blog.bfccomputing.com/ VCard: http://bfccomputing.com/vcard/bill.vcf
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
