I am using net-snmp on an embedded device with relatively limited memory
resources (64Mb to be specific).
I started noticing that the process of snmpd took more and more memory on
each trap I sent from the device. The process reached around 20Mb of memory
and then the memory usage stopped to increase. This memory usage was off
course too big for my device.
Finally (using the great help of Bill Fenner) I understood the memory was
taken by the notification mib module. I removed it from the modules and it
solved my problem.
In my opinion adding this module as the default configuration is very bad
for embedded devices (who most of the time do not really need the
notification mib) and it creates a scenario where snmpd takes a lot of
memory without the developer aware of it or the reason for this.
The very least that needs to be done is to add some kind of
documentation/remarks in the net-snmp site, package help (maybe in help of
configure) that notification mib module (notification ,notification-log-mib
modules) requires large amount of memory from the device its running on.
This can solve a lot of head-aches for future embedded developers using
net-snmp.
Comments / remarks/ suggestion are welcome
Ofer Avitzur
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
