The subcommand "shutdownpending" is missing from the
"ns_info" command. This should invoke the C API
Ns_InfoShutdownPending() and return a boolean value.
One specific use case where the [ns_info
shutdownpending] is important: long-running worker
threads running in forever-loops need to know when to
terminate at server shutdown. Especially important are
scheduled procs that run in separate threads from the
main "sched" thread.
Right now, those threads will cause the server to wait
until "shutdowntimeout" (default 20 sec) then the
server will abend with the following fatal message:
[17/Sep/2004:00:30:22][13849.79][-driver-] Fatal:
driver: trigger recv() failed: Socket operation on
non-socket
Those threads need to be implemented to periodically
check (at least as frequently as once every
shutdowntimeout seconds) for [ns_info shutdownpending]
true, and if so, terminate themselves.
For threads which run C procs, they should use the
Ns_InfoShutdownPending() C API which already exists to
do the same.
Logged In: YES
user_id=21885
This isn't really a bug but rather an RFE. Moving it to the
appropriate Tracker.