aboutsummaryrefslogtreecommitdiffstats
path: root/lib/snmp/doc/src/getnext4.ps
diff options
context:
space:
mode:
authorMicael Karlberg <[email protected]>2011-02-25 13:54:07 +0100
committerMicael Karlberg <[email protected]>2011-02-25 13:54:07 +0100
commit931e775de52e6e335a10759c7fb3e0f8efea21d3 (patch)
tree79afd23e811719acaaf527707f9edf9a585de88d /lib/snmp/doc/src/getnext4.ps
parent02b9003b697474ef6b7e07a6f7eebd6105d4497f (diff)
parentca6e87e84dae13b6ebe15ca67bf98a0245f25857 (diff)
downloadotp-931e775de52e6e335a10759c7fb3e0f8efea21d3.tar.gz
otp-931e775de52e6e335a10759c7fb3e0f8efea21d3.tar.bz2
otp-931e775de52e6e335a10759c7fb3e0f8efea21d3.zip
[agent] When calling
snmp_view_based_acm_mib:snmp_view_based_acm_mib:reconfigure/1 on a running node, the table vacmAccessTable was not properly cleaned. This meant that if some entries in the vacm.conf file was removed (compared to the "current" config), while others where modified and/or added, the removed entrie(s) would still exist in the vacmAccessTable table. Merge branch 'bmk/snmp/vacmAccessTable_cleanup/OTP-8981' into bmk/snmp/snmp419_integration/OTP-9068 Conflicts: lib/snmp/doc/src/notes.xml lib/snmp/src/app/snmp.appup.src lib/snmp/vsn.mk
Diffstat (limited to 'lib/snmp/doc/src/getnext4.ps')
0 files changed, 0 insertions, 0 deletions