On Tue, Aug 14, 2007 at 11:26:20AM +0200, Lennert Buytenhek wrote: > On Tue, Aug 14, 2007 at 09:50:30AM +0200, Lennert Buytenhek wrote:
> > There have been db4 corruption reports on ARM (specifically, > > environment file corruption) as long as I can remember. > For one, I keep ending up with a negative number of lock objects. > 4294M Number of current lock objects (4294967287) > 4294M Maximum number of lock objects at any one time (4294967295) > Note that berkeley db's shared memory queue implementation uses -1 > as end-of-list indicator. That might be a clue. Is this with oldabi or with eabi? eabi build do not fail the same test (env007: db open:invalid argument) but rather with: r: mutex: unknown command This error is common on arm, armel and s390 atleast. -- "rm -rf" only sounds scary if you don't have backups -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
