Hi,
My apologies if this question has been dealt with before - I did a quick search
but couldn't find anything.
>From my understanding when the SNMP agent is shut down (or when a config save
>is requested via SNMP-SET), the persistent configuration file is re-created
>using the currently configured data. This works fine for USM since usmUser
>directives are placed in this file. However VACM directives such as "access",
>"group", "rwuser" and "rouser" seem to be stored in the main configuration
>file, which is not regenerated by the agent (unless I'm missing something).
So my question is: How do I update the configuration files if VACM changes are
made via SNMP requests, so that following a reboot the changes will remain
within the agent? Is there a way to force the agent to regenerate both
configuration files, or am I totally misunderstanding something?
Thanks for any help.
Harvey Shepherd
------------------------------------------------------------------------------
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
