>>>>> On Thu, 22 Sep 2011 02:16:48 +0000, Harvey Shepherd >>>>> <harvey.sheph...@aviatnet.com> said:
HS> However VACM directives such as "access", "group", "rwuser" and HS> "rouser" seem to be stored in the main configuration file, which is HS> not regenerated by the agent (unless I'm missing something). Correct, we do *not* store any data that comes from the config lines like the above. HS> So my question is: How do I update the configuration files if VACM HS> changes are made via SNMP requests, so that following a reboot the HS> changes will remain within the agent? Is there a way to force the HS> agent to regenerate both configuration files, or am I totally HS> misunderstanding something? The agent already does what you want: internally it marks the row as "created from a config file, and thus don't save it" vs "created from SNMP SETs and thus I need to save it". Only rows in the table that were created via SETs will get written to the dynamic file. In fact, if you walk the table you'll see rows marked with a rowstorage type as "permanent". These are the ones that came from the config file. Any others you created via SETS will be "volatile" or "non-volatile" instead. And the "non-volatile" ones will get stored to the persistent storage file. -- 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
