>>>>> On Mon, 27 Jun 2011 15:49:01 +0100, "Lewis Adam-VNQM87" >>>>> <vnq...@motorolasolutions.com> said:
LA> I think our main concern was the possibility of memory leaks. Being an LA> embedded product, it's not simply a case of killing the process and LA> restarting it so while we want to offer the flexibility of updating LA> ip-based, mac-based, and text-string based SnmpEngineIDs, we also want LA> the unit not to be rebooted unless absolutely necessary. If I understand LA> it correctly, we should be able to destroy all the vacm and usm entries LA> and reload them with default users. Hopefully the pain of re-entering LA> user information will discourage people from changing the SnmpEngineID LA> on a regular basis. Definitely, discouragement of changing it is tactic one :-) -- Wes Hardaker Please mail all replies to net-snmp-coders@lists.sourceforge.net ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of 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-d2d-c2 _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
