Which is kind of my point. I tried to use CheckFiles to test for certain conditions,
if CONDITIONS then ALERT but what I get is, if CONDITIONS or ERROR then ALERT While this makes sense perhaps for a ping check it isn't that useful for testing for the presence of something (rather than testing for the absence of a problem), if you see what I mean. With a service check, you want an alert if a service is not running, I agree, but with CheckFiles I wanted an alert when something IS there, which is ever-so-slightly different. Not anticipating the possible ERROR results in extra alerts (yep, we use %e and other parameters in alerts). //Steve -----Original Message----- From: Dirk Bulinckx [mailto:[EMAIL PROTECTED] Sent: den 11 april 2006 09:55 To: Servers Alive Discussion List Subject: [SA-list] RE: [SA-list] False positives If a check is not OK, then it's down, that's indeed the way it works. The "down" word should be interpreted as being " no confirmation of it being UP". Within the alert using the %e parameter will show the reason of the down. Then you could see (for example) that an NT service is seen as being down because of "Access Denied" (meaning that at the time of the check we got a access denied back from the OS and as such can't confirm that the service is running). To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
