> On Thu, 22 Sep 2011 21:42:08 +, Harvey Shepherd
> 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 m
> 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> misunde
> On Thu, 22 Sep 2011 02:16:48 +, Harvey Shepherd
> 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*
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 confi
