<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59"> <TITLE>RE: [Nagios-users] Trap reset script</TITLE> </HEAD> <BODY>  Hi Steve, That decision was made a while ago and I probably though about using the freshness checking. I guess my idea was that a trap should stay on until it is handled. For various reasons we're not really using traps yet, but the system is there for the day we start using them (soon hopefully). Maybe after we use them a bit we'll decide on changing to "Self-reset" traps. Thanks for bringing is on though, that's a good suggestion... :) Thomas -----Original Message----- From: Steve Shipway [<A HREF="mailto:s.shipway@auckland.ac.nz">mailto:s.shipway@auckland.ac.nz</A>] Sent: Tue 13-Mar-07 19:51 To: Thomas Guyot-Sionnest; nagios-users@lists.sourceforge.net Subject: RE: [Nagios-users] Trap reset script > It will look up the status and command files from the Nagios config, parse > the status and then force an active check for services matching these > criterias: > 1. Should not be scheduled to be checked > 2. Has active checks enabled Is there a reason why you are not using the Nagios freshness checking to achieve this? We have a similar system, with SNMP alerts coming into Nagios, and use the Freshness Check to set the status to OK after a set period of time. Services are set to volatile, max_checks=1, so they notify immediately on receiving a trap no matter what the current state. Steve </BODY> </HTML>