> (which I think was done to work around some ancient bug in an ancient > version of the nsoracle driver) then you get the problem.
I think the problem was in the oracle library (OCI), but it's been a long, long time. > I imagine on Linux it manifests differently; on Solaris I got the EINVAL > return from pthread_cond_timedwait (of course it isn't documented that > this can mean a bad time, it usually means a bad pointer) Oh, ignore my last post, I see know that I'm paying attention again :) The billion seconds added to the current time when the database handle's created is causing the problem, with Solaris being nice enough to toss an error, Linux just screwing up. And a billion seconds is in the neighborhood of 31-32 years. Y2.038K indeed! -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
