There seems to be a memory leak in the code for sending snmp v2 traps.
I have a few traps that are sent many times a minute in certain
situations and when those traps are being sent frequently the memory
footprint of net-snmp gets larger and larger. within the code for
sending my trap, if I
I am going to use logmatch, but dont know how to
Could anyone help?
Kevin SZ
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server
Mark Little wrote:
I am seeing a crash on startup trying to run snmpd from net-snmp 5.2.1 on
MontaVista 4.0.1 (linux kernel 2.6.10) that *appears* to be in the ioctl
calls to get the interface speed. The end of the output with -V and -DALL is:
Can you please try 5.2.3.pre3 (or 5.2.3.rc1 if
although I have this in my snmpd.conf file
rwuser snmp
rwcommunity public
trapcommunity public
trapsink localhost
agentSecName internal
rouser internal
-
with netsnmp 5.3.0.1 default install from tarball
I still am seeing this when I set up a mteTriggerEntry and it does its
I am running NET-SNMP version 5.2.2 and when I try and get the value for my
swap space, I get -2146828126 which is very incorrect. I have around 1gig of
swap space and was wondering if that could be the problem, that it was to
large?
What platform?
This communication is intended for the use of
Net-SNMP 5.3.1.rc2 has been released and placed on our website. It is
the 2nd release candidate for the 5.3.1 release. The biggest changes
since rc1 have been:
- new perl number version numbers to make them CPAN compatible
- UDP tables have been fixed for byte ordering issues
We expect