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 relative time, then you want to find the caller who's passing in the bad value and fix it. However, I'm not convinced that a bad time value could cause the error result you are seeing. You might check that further. Mark Rob Crittenden wrote on 2/23/2004, 11:18 AM: > It's failing because the timeout isn't setup properly. The timeout value > to pthread_cond_timedwait() is based on an absolute time, not a relative > time. So I guess the right thing to do is modify Ns_CondTimedWait() to > fetch the local time and add the timeout to that. > > I was able to duplicate the problem myself and this patch resolves it. I > guess the next step is to add a configuration option for the time to > wait. -- 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.
