Hi,
I have a problem with the persistent data. Basically with the password, which
it is not saved at runtime.
Let's say that one user has the password "passwd_default". I change the
password (with snmpusm command) to "passwd_new" and the change is correctly
applied. From this point there are two cases: 1) If I stop the snmpd in a
controlled way and then restart it, the password is the expected one
("passwd_new") 2) If the snmpd is killed (kill -9, Ctrl+C...) and then
restart it, the password comes back to the previous one ("passwd_old")
I've checked the persistent file (where the password is present but encrypted)
and no change has been applied to this file after commanding the password
change with snmpusm.Searching information, I found some comments related to
this issue, explaining that the daemon does not dump or synchronize runtime
data to disk until it is stopped.
Does anyone know anyway to avoid this issue and force the snmp daemon to dump
inmediatelly this information to the disk?I've seen something about setting the
flag versionSavePersistentData.0 to 1 after changing the password, but I would
prefer to use configuration settings at start-up (if possible), in order to
avoid the use of two commands to change the password.
Thanks in advance
------------------------------------------------------------------------------
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. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
