This should be in the code now -- check the shutdownPending static
var in nsd/sched.c. The behavior should be that as soon as shutdown
begins, this flag is set an no new sched procs can be created or
kicked off. There could be a bug in there.
Of course if a thread-based proc is running
On Monday 18 July 2005 17:53, Janine Sisk wrote:
Wouldn't it make sense for the scheduler to stop starting up new proc
runs once it knows the server is shutting down? It's not like these
are long running things; they are starting up very frequently because
they only run for a few seconds
On Mon, Jul 18, 2005 at 08:35:21PM -0400, Dossy Shiobara wrote:
I've filed RFE #1029889 that will introduce [ns_info shutdownpending] so
http://aolserver.com/sf/rfe/1029889
Well, that sounds like a good idea, but can't you do that already with
ns_atshutdown if you need to? I've used code
On 2005.07.18, Janine Sisk [EMAIL PROTECTED] wrote:
We've just moved a bunch of sites around and in the process they all
got upgraded to 4.0.10. One of them is exhibiting some odd behavior
and I'd like to know if anyone has any idea what the problem might be.
...
etc, etc and so forth.
On Jul 18, 2005, at 5:35 PM, Dossy Shiobara wrote:
If you look in your server logs from when it was running 4.0.1, at
shutdown you probably saw an fatal error being logged. If so, I
suspect
you were taking advantage of SF Bug #1029918:
Nope, actually not:
