Thanks for the reply Wes. I think our main concern was the possibility of memory leaks. Being an embedded product, it's not simply a case of killing the process and restarting it so while we want to offer the flexibility of updating ip-based, mac-based, and text-string based SnmpEngineIDs, we also want the unit not to be rebooted unless absolutely necessary. If I understand it correctly, we should be able to destroy all the vacm and usm entries and reload them with default users. Hopefully the pain of re-entering user information will discourage people from changing the SnmpEngineID on a regular basis.
Regards, Adam ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
