>>>>> On Fri, 08 Oct 2004 23:54:33 +0200, Thomas Anders <[EMAIL PROTECTED]> said:
>> Hmm... It should definitely use the old engineID... The agent does,
>> so I'm confused why the trapd is acting differently.
>> did you compare the two?
Thomas> The early generation of an engineID (before reading the config
Thomas> files) in snmptrapd is most likely a side effect of an early
Thomas> initialization routine (init_*). I haven't compared with snmpd
Thomas> yet, but it's definitely broken in snmptrapd.
Thomas,
This bug seems specific to your environment. I've tested trapd on my
end with no problems. I put this:
{
u_char *newID = malloc(1024), *outbuf = malloc(1024);
size_t len = 1024;
len = snmpv3_get_engineID(newID, len);
snprint_hexstring(outbuf, 1024, newID, len);
fprintf(stderr, "eid: %s len=%d\n", outbuf, len);
}
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.
--
Wes Hardaker
Sparta
-------------------------------------------------------
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
