My vote is to put it in too. It sounds particularly useful on Win32 where its harder to do the watchdog type stuff, and where quite honestly you need a second watchdog watching the first watchdog ;-)
In older AOLservers there seemed to be a '-k' command line option to kill the running server. Could that be re-instated at the same time as a way of signalling to the server "this is an intentional STOP signal" so that it doesn't automatically restart? (I'd have thought this could be done with real SIGNALS, but wouldn't necessarily have to work that way - it could be a request to a configurable URL e.g. /STOP that changes some flag internally and shuts the server down. For the security conscious this could be password protected, require some cryptographic data along with the request, could be limited to request from the localhost etc. etc.) > -----Original Message----- > From: AOLserver Discussion [mailto:[EMAIL PROTECTED] Behalf > Of Scott Goodwin > Sent: Thursday, June 05, 2003 6:54 PM > To: [EMAIL PROTECTED] > Subject: Re: [AOLSERVER] [ aolserver-Feature Requests-746579 ] Server > instance controller process > > > This is a very useful feature that would be very helpful for new users > especially. I think it's so good, I would prefer to see it integrated > such that you trigger it with a command line flag to nsd at start time. > Many of you use other tools to perform watchdog activities, which is > great. But others in the community who aren't as outspoken as the > experts on this list might be running one-shot web sites where this > feature would reduce the complexity of monitoring and restarting > AOLserver should it fail. > > My vote is to put it in. > > /s. > > > On Saturday, May 31, 2003, at 12:07 PM, Zoran Vasiljevic wrote: > > > On Saturday 31 May 2003 18:43, you wrote: > > > >> How many lines of code and how many man-hours will it take to > >> implement > >> in C? How long will it take to review all the code to ensure you've > >> neither introduced any new bugs or otherwise broken already existing > >> code? > > > > We have it running for about 3 years already. No need to develop > > anything > > since it is already there. It does not change anything related to the > > main > > server so it needs no extra testing. > > It is just an C-equivalent of your shell-script and it alows you to: > > > > nsd -s -t config.tcl > > > > and forget about it. It logs worker start/stop/restart in system > > logfile > > so its easy to track. > > > > > >> Also, as a stand-alone script or program, folks running even older > >> AOLserver 3.3.x could take advantage of it, rather than being forced > >> to > >> upgrade to either 4.x or 3.5.x ... or were you planning to backport > >> this > >> change all the way back? > > > > Ah.... > > > > Seeing all those responses... I think I'll just keep our own patched > > nsd copy and leave all as-is. It took me more time to write all those > > anwers, than to write the small C-routine we're talking about. > > If everybody is happy with shell/daemontools/whatever there is no > > reason for me to do anything here, obviously. > > Apparently, we have a very different usage pattern than most of the > > other > > users... > > > > Cheers, > > Zoran > > > > > > -- > > 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/ > > > > > -- > 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/ > -- 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/
