Let me toss out an alternate suggestion: how about a command line switch that will disregard all errors for the first check cycle? So if you ran it with salive /skipfirst, let's say, it wouldn't send any alerts during the first run of checks? Would that make people happy? Then, have an option where you can start ServersAlive as a service that way by default?
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, September 04, 2003 8:09 AM To: [EMAIL PROTECTED] Subject: RE: [5] RE: [SA-list] change in state But your suggestion is almost impossible when you run as a service.... If an alert has been generated, the app should assume it was received.. --- Troy Bruder, Manager - Hosting and Microsoft Services APT Information Technology Consultants 7540 Windsor Dr. STE 204 Allentown, PA 18195 Phone 610.366.1100 -or- 888.2.GET.APT http://www.aptconsulting.com "Jason Passow" <[EMAIL PROTECTED] To: <[EMAIL PROTECTED]> > cc: Sent by: Subject: RE: [5] RE: [SA-list] change in state [EMAIL PROTECTED] stone.nu 09/03/2003 04:56 PM Please respond to salive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
