Hi, Thanks!
I was able to get it going by minimizing the access configuration and cleaning up the monitor call, as you "pinged" below. I caught the "-i" (a Doh! moment) mishap just before leaving for home, wasn't sure I'd gotten it, though. Now I can't get "proc/procfix" to work: may soon see another thread about that. I have not yet mastered the black art of remote gdb. I'll keep you posted (I'm sure). Thanks again. D. > > So you do see the VACM message (plus memory leak) if you have > two monitor lines: > > monitor -e prRestartMeter_service -u disman -r 1 -i prCount.3 < 1 > monitor -e notMeter_service -u disman -r 1 -i .... "meter_service > down" prCount.3 < 1 > > but not if you've just got the second line? > The notification > <ping> > Of course - the first line (causing the problem) is missing the "NAME" > field. > So it's probably taking "prCount.3" as the name of the entry, and "< 1" as > the expression to monitor. > > I'm a little surprised that the agent isn't complaining about this > expression, > but I suspect that if you add a name field "restart_meter", things should > work OK. > > Try it. > > Dave > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ 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
