Thomas Anders wrote:
Even though snmptrapd handles the "oldEngineID
0x80001f888096c4781a71d0c43e"
from the config file, it insists on generating a new one
(e.g. 0x800007e58023572f3955f66341) soon thereafter in
lcd_set_enginetime().
The problem seems to be that
- init_usm() calls setup_engineid() before reading config files
resulting in an initial UCD_RND-based engineID
- the "oldEngineID" handler oldengineID_conf() just puts the string
into the global oldEngineID variable, *not* changing the
global engineID variable
What's the rationale behind this?
Shouldn't oldengineID_conf() call setup_engineID() just like
engineID_conf() already does?
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Net-snmp-coders mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
