On 2004.02.23, Taguchi Takeshi [EMAIL PROTECTED] wrote:
New error occurs.
[23/Feb/2004:15:13:51][84562.134557696][-main-] Notice: driver:
starting: nssock
nsthreads: pthread_cond_timedwait failed in Ns_CondTimedWait:
Operation not permitted
Abort
I think error codes for
Hi,
I upgraded to 4.0 (and also upgraded nsora to 2.7), and now aolserver
fails to ever connect to oracle if it is started before or during the
oracle startup. I'm using Mac OS X 10.2.8. I believe this used to
work. I am trying to work around by changing my system startup
scripts, but I wanted
I've been running PHP under AOLserver 4.0 GM1 solely because we need a decent
webmail solution, and squirrelmail seems to do the trick.
I put my nsd processes under djb's supervise, to ease
starting/restarting/stopping and so they're brought back up in case they
die.
I've been noticing that the
Or here I am with a better fix rather than changing the semantics of an
existing function (what was I thinking!?).
Still using Dobby's patch, change the way the timeout is set from
timeout.sec = 10;
timeout.usec = 0;
to
Ns_GetTime(timeout);
timeout.sec += 10;
rob
Rob Crittenden
I've been noticing that the nsd with PHP goes into a
cpu-eating mode after
Roberto,
By chance are you using nsopenssl on that box as well? We are seeing
issues where 4.0.2 threads will run away. We still haven't tracked this
one down.
They don't seem to want to run rampant if nsopenssl is
On Mon, Feb 23, 2004 at 11:49:08AM -0500, Kevin Murphy wrote:
I upgraded to 4.0 (and also upgraded nsora to 2.7), and now aolserver
fails to ever connect to oracle if it is started before or during the
oracle startup. I'm using Mac OS X 10.2.8. I believe this used to
That's nothing new,
I don't follow this. The Ns_CondTimedWait is defined to take an
absolute time value. (See
http://www.aolserver.com/docs/devel/c/api/c-ch49.htm#551016 ) So, you
don't want to change it to do adjustments assuming that what's given is
a relative time.
If what's going wrong is that it's getting a
By the way: It would be more proper to use the Ns_IncrTime api to
manipulate this timeval. E.g.,
Ns_GetTime(timeout);
Ns_IncrTime(timeout, 10, 0);
This makes more sense once the constant delta seconds is replaced by a
configurable value.
Rob Crittenden wrote on 2/23/2004, 11:58 AM:
On 2004.02.23, Rob Crittenden [EMAIL PROTECTED] wrote:
Or here I am with a better fix rather than changing the semantics of an
existing function (what was I thinking!?).
Seriously! When I saw the patch against pthread.c, I nearly choked.
:-)
Still using Dobby's patch, change the way the
On 2004.02.23, Mark Page [EMAIL PROTECTED] wrote:
By the way: It would be more proper to use the Ns_IncrTime api to
manipulate this timeval. E.g.,
Ns_GetTime(timeout);
Ns_IncrTime(timeout, 10, 0);
This makes more sense once the constant delta seconds is replaced by a
configurable
On Mon, Feb 23, 2004 at 10:13:58AM -0700, C. R. Oldham wrote:
I've been noticing that the nsd with PHP goes into a
cpu-eating mode after
Roberto,
By chance are you using nsopenssl on that box as well? We are seeing
issues where 4.0.2 threads will run away. We still haven't tracked this
11 matches
Mail list logo
