On 2004.02.23, Taguchi Takeshi <[EMAIL PROTECTED]> wrote:
> [23/Feb/2004:10:53:02][67435.134559744][-sched-] Notice: sched: starting
> [23/Feb/2004:10:53:02][67435.134557696][-main-] Notice: driver: starting: nssock
> [23/Feb/2004:10:53:02][67435.134557696][-main-] Warning: driver: startup timeout:
> nssock
> [23/Feb/2004:10:53:02][67435.134557696][-main-] Warning: prebind: closed unused:
> 10.0.0.6:80 = 3
> [23/Feb/2004:10:53:02][67435.134560768][-nssock:driver-] Notice: starting
Wow, why is it taking more than 10 seconds to start the nssock driver?
(That's how long the startup timeout is.)
Maybe I need to put the mutex around more of the DriverThread startup
code -- get the patch again (the file is updated on my server). The
relevant change is:
821 Ns_MutexLock(&drvPtr->lock);
822 drvPtr->sock = Ns_SockListenEx(drvPtr->bindaddr, drvPtr->port,
823 drvPtr->backlog);
824 if (drvPtr->sock == INVALID_SOCKET) {
825 Ns_Fatal("%s: failed to listen on %s:%d: %s", drvPtr->name,
826 drvPtr->address, drvPtr->port, ns_sockstrerror(ns_sockerrno)
);
827 }
828 Ns_SockSetNonBlocking(drvPtr->sock);
829 drvPtr->started = 1;
830 Ns_CondBroadcast(&drvPtr->cond);
831 Ns_MutexUnlock(&drvPtr->lock);
Basically, move the Ns_MutexLock(&drvPtr->lock); which used to come
right before the "drvPtr->started = 1;" line to all the way right before
the "drvPtr->sock = ..." line. Maybe it's easier to just check out CVS
HEAD again and apply the new patch clean. :-)
-- 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.
