On Mon, 2008-06-09 at 10:14 -0700, Chris Larson wrote: > On Thu, 2008-06-05 at 22:51 +0200, Thomas Anders wrote: > > Chris Larson wrote: > > > I've run into a segmentation fault in net-snmp version 5.4 on our > > > product, when there's a cpuIdle > or < alert set up in snmpd.conf. > > > > Would it be possible for you to try with 5.4.2.pre1 instead or is it too > > much integration work? This bug may have been fixed already, so it may > > be worth the effort. > > Okay, just tested with 5.5.dev, svn HEAD as of last friday. Same > behavior. I'm trimming down the snmpd.conf to show the smallest test > config in which I see the problem.
Current config that reproduces the segfault for me: agentSecName internal authtrapenable 1 rouser internal rwcommunity foo syscontact me syslocation here trap2sink 127.0.0.1 hostname_1 monitor -r 5 "Clear: CPU idle above 10%" ssCpuIdle > 10 monitor -r 5 "Memory available less than 128MB" memTotalFree < 128000 -- Chris Larson Dedicated Engineer Montavista, Inc. Email: clarson AT mvista DOT com Email: clarson AT kergoth DOT com ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
