aboutsummaryrefslogtreecommitdiffstats
path: root/erts
diff options
context:
space:
mode:
authorSiri Hansen <[email protected]>2012-09-21 10:09:49 +0200
committerSiri Hansen <[email protected]>2012-09-21 10:09:49 +0200
commitc73625b031181d8c0ca65760ae44a1dbae4400df (patch)
tree547d92fc8db1ebc487c8308f1d923f278a593928 /erts
parent53b3095adb6478c63da1ef5ef7f3006e4fd614ef (diff)
downloadotp-c73625b031181d8c0ca65760ae44a1dbae4400df.tar.gz
otp-c73625b031181d8c0ca65760ae44a1dbae4400df.tar.bz2
otp-c73625b031181d8c0ca65760ae44a1dbae4400df.zip
[common_test] Use ct_snmp 'agent_vsns' config value in snmp app config
OTP-10432 Config parameter 'agent_vsns' in ct_snmp was ONLY used in call to snmp_config:write_agent_snmp_files. There it is only used for deciding if usm config shall be written (if v3 is included) or not. The value of 'agent_vsns' was NOT added to the snmp application's agent configuration, so the snmp application's own default value would be used - this is [v1,v2,v3]. The result was that if v3 was not included in 'agent_vsns', then usm.conf was not written, but when starting the agent it would complain that this file did not exist since snmp's default versions are all [v1,v2,v3]. This has been corrected - the 'agent_vsns' value is now inserted in the snmp application agent configuration as {versions,AgentVsns}.
Diffstat (limited to 'erts')
0 files changed, 0 insertions, 0 deletions