>>>>> On Thu, 22 Sep 2011 21:42:08 +0000, Harvey Shepherd >>>>> <harvey.sheph...@aviatnet.com> said:
HS> Thanks Wes. I see how this is all handled via SNMP_CALLBACK_STORE_DATA HS> callback registrations now. Will this mechanism also take care of any HS> non-volatile rows that are destroyed dynamically as well? The callback merely allows the rows to be written to disk. If anything was destroyed, the new file written to disk won't contain the destroyed rows. (IE, the responsibility of the callback is to save *all* data, not just new data; thus old data no longer around gets nuked automatically) -- Wes Hardaker Please mail all replies to net-snmp-coders@lists.sourceforge.net ------------------------------------------------------------------------------ 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. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
