On Mon, 2006-03-27 at 15:46 -0500, Jean-Sebastien Morisset wrote: > If I stop cron using the following in my snmpd.conf file: > > monitor -S -r 128 -o prNames -o prErrMessage "procTable" prErrorFlag != 0 > > Then it work fine,
As expected - good. > BUT if I use this _instead_: > > monitor -S -r 128 -o prNames.2 -o prErrMessage.2 "procTable.2" prErrorFlag.2 > != 0 > > Then it doesn't work. Try monitor -I -S -r 128 .... The "-I" flag indicates that this monitor entry refers to a specific instance, rather than a wildcarded object. > I had to split the procTable because the standard > monitor would return erroneous errors for running processes. For > example: > > mteTriggerFired trap received from gessolx1.dev.me.org: > procTable .1.3.6.1.4.1.2021.2.1.100.2 1 cron > > I'd set "proc cron 1 1" so a trap shouldn't have been sent. What does walking the procTable show in such a situation? It might be worth tweaking the "monitor" line to report the prErrorFlag and prCount values as part of the trap, so you can see what's actually happening. Dave ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
