Wes Hardaker wrote:
This bug seems specific to your environment. I've tested trapd on my
end with no problems. I put this: [...]
at multiple points (finally all the way down in the "running" loop)
and it always showed the same value over and over. I restarted. I
moved aside the persistent file, which showed it created a new
engineid. Stopped it and restarted it and it kept the new one.
AFAICS, "-C" seems to be the culprit. When either using SNMPCONFPATH
or "-c /path/to/snmptrapd.conf" (*without* "-C"), the oldEngineID
directive works as expected.
However, with "-C -c /path/to/snmptrapd.conf,/var/net-snmp/snmptrapd.conf"
things fail miserably in this regard since the config files are read
too late then (when a fresh engineID has already been generated).
Patch 1042139 fixes this. If you know of a better way to fix this,
please share your thoughts.
I'd tend to argue that "-C -c" should load the config files at the
same time as with the other approaches. Comments? Thoughts?
+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
