On 29 November 2011 17:15, Ofer Avitzur <[email protected]> wrote: > I am using net-snmp on an embedded device with relatively limited memory > resources (64Mb to be specific).... > In my opinion adding this module [notification MIB] as the default > configuration > is very bad for embedded devices
I think our expectation is that those aiming at embedded devices would start with the guidance given in the FAQ entry "How can I reduce the memory footprint?" The second suggestion listed there is to use '--enable-mini-agent', to set up an agent with the absolute minimum of MIB modules - and then add any extra MIB modules that would be required. That seems a more appropriate approach for limited-memory devices, rather than advising you to strip out individual modules. But I'll certainly have a look at adding something about the effects of the Notification MIB to the FAQ Dave ------------------------------------------------------------------------------ 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
