Indeed they are not. I'd add some more confusion by extending the second to "Are you *correctly* answering requests?"
So, the solution window may vary between a very simple dumb one "Are you still running?" to some AI-based custom behaviour, which is, by it's very nature, hard (if possible at all) to properly generalize.
Now, reality is: there is *none* of the above in nsd as-is now!
I have been able to make do quite adequately with the ACS suggested monitoring mechanism, which basically just ns_httpgets a list of URLs and expected results and compares the actual results with the expected results and restarts AOLserver on failure.
I use a very simple static page to test if basic request processing is working, and then a very simple page involving a db query to determine if the db is up and their is connectivity between the db and aolserver.
At the risk of adding complexity to the parent process, I wouldn't mind seeing such a monitoring facility added to the parent process.
Jerry
-- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
