On 2004.02.23, Taguchi Takeshi <[EMAIL PROTECTED]> wrote: > I've applied new patch, and tested it. > But I've got same result.
Yeah, I'm not too keen on why those mutexes are even being used around the readers of the values -- I think the Ns_CondTimedWait() should be done without grabbing the Ns_Mutex and only grab the mutex when you want to read the value. But still, only one thread writes and the other thread reads, so the mutexes aren't really necessary. > In NsWaitDriversStartup(), I feel something wrong. > Because, driver startup is timedout. > It means Ns_CondTimedWait() exits abnormaly .... Is it correct? Well, it means that Ns_CondTimedWait() is exiting normally, but it's exiting because the timeout has elapsed. Try deleting the lines "Ns_MutexLock(&drvPtr->lock);" and "Ns_MutexUnlock(&drvPtr->lock);" lines from NsWaitDriversStartup() in nsd/driver.c, and see if that fixes the problem. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- 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.
