I fixed it by simply changing my MaxOpen/MaxIdle settings to "0" which
is interpreted as "forever" which is probably what the original "one
BILLION seconds" was undoubtedly intended to be.
It probably wouldn't hurt for Ns_AdjTime (in nsthread/time.c) to check
for negative seconds and have it fail in a nicer manner, but that
problem won't affect anyone for years :)
-J
Janine Sisk wrote:
On May 19, 2006, at 1:04 PM, 'Jesus' Jeff Rogers wrote:
The only bug is that Ns_CondTimedWait doesn't do any wraparound on the
time parameter. All the same, I've been enjoying telling people that
I hit my first y2038 bug.
So are you saying you've fixed it, or just that you've narrowed it down
to this? If you've fixed it, do tell! :)
janine
--
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.
