On 14/09/2001, Igor Khasilev <[EMAIL PROTECTED]> wrote To [EMAIL PROTECTED]:
> > Result: db_appinit reports from berkeley_api.c:
> > if (db_appinit(dbhome, NULL, dbenv,
> > DB_CREATE|DB_THREAD) ) {
> > my_xlog(OOPS_LOG_SEVERE, "open_db(): db_appinit(%s) failed: %m\n",
>dbhome);
> > }
Ok, i put debugging code into db-2.7.7 and found out, that the flags
are actually causing the trouble. db-2.7.7 fails to detect the
spinlock capabilities on OpenBSD, and thus the DB_THREAD is causing
the failure. And also therefor there is never a file open in the
ktrace, cause the function is failing in the very first point.
So, besides the misleading error reporting, it's not Oops fault in first
place. Btw, db_appinit is a bit weird, there are 4 functions which all
could cause the same errno, so that's a bit difficult to handle in a
calling program.
I *guess* the problem is the same for gigabase, but I first hack db-2.7.7
to compile w/ proper spinlocks (relativley short hack in mutex/mutex.c).
ciao
--
Philipp Buehler, aka fips | sysfive.com GmbH | BOfH | NUCH | <double-p>
#1: Break the clue barrier!
#2: Already had buzzword confuseritis ?
=====================================================================
If you would like to unsubscribe from this list send message to
[EMAIL PROTECTED] with "unsubscribe oops-eng" in message body.
Archive is accessible on http://lists.paco.net/oops-eng/
