On Nov 29, 2007, at 7:34 PM, Yuri wrote:
Quoting Garrett Cooper <[EMAIL PROTECTED]>:
Yes, it's partly caused by pkgdb and/or how Ruby / pkgdb
handles the
DB I think...
1. What type of BDB structure do you use [most likely btree(1) --
says this during the pkgdb rebuild..]?
bdb_btree
2. What version of BDB are you using (1.85, 2.x or 4.x) [(cd
/usr/ports/ports-mgmt/portinstall && make config) will give you
that info]?
4.x
3. uname -a says?
BSD xxx.xxx.xxx 7.0-BETA3 FreeBSD 7.0-BETA3 #1: Tue Nov 27 13:11:12
PST 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386
Yuri
I'd try using BDB 1.85 as it appeared to be a bit more stable than
4.x (at least that's what I remember from using it..).
You'll have to delete the .db files and fix things via portsdb and
pkgdb (IIRC), but after that it's essentially the same song and dance..
Interrupting pkgdb while it's doing its thing will corrupt the .db
files though as BDB isn't an atomic database API..
Cheers,
-Garrett
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
