proc sleepy { } {
ns_log Notice "Sleeping for 120 seconds." ns_sleep 120 ns_log Notice "Finished sleeping."
}
ns_schedule_proc -thread -once 30 sleepy
I am using daemontools to send signals to AOLserver, but the same could be accomplished with shell commands.
When I watch the log, I see the first log notice and used: 'svc -d'. (send sigterm then sigcont and doesn't restart the process) The -sched- thread that kicks into action says 'waiting for event threads...'. My scheduled proc sleeps for 120 seconds and then prints the second log notice. But then -sched- keeps on waiting. Even when the event thread is finished, it still hangs.
Using svc -k then svc -d sends sigkill, sigterm, sigcont and this seems to work.
The behavior differs from 3.5.1, which waits for the threads for a short time, then kills them and returns to finish shutting down the server.
OpenACS developers have indicated this is a showstopping bug. The effect is that if you try to reboot your server, AOLserver will never exit. This could prevent other software, such as Oracle, from shutting down, which totally screws your reboot/shutdown of the entire server.
Also if you send sigterm, sigcont, sigkill, the result is the server goes down, but some of the shutdown log messages are missing.
--Tom Jackson
I. To remove yourself from this list:
Send a message to "[EMAIL PROTECTED]" with the following text in the BODY of your message:
signoff aolserver
II. For a complete list of listserv options please visit:
http://listserv.aol.com/
III. For more AOLserver information please visit:
http://www.aolserver.com/
