> I am sorry but still I didn't find
> init_agent("snmptrapd") in snmptrapd.c of ucd-snmp-0.4.2.5
OK.
Both Wes and I will have been looking at the v5 code.
The v4 line is rather old now, and is no longer being developed.
> init_snmp("snmptrapd") is there.
> And I am also calling this function. Does this routine also do same as
> init_agent?? or should I explicitly use init_agent instead od init_snmp
> or BOTH?
No - the two init routines are concerned with different things,
and it isn't a matter of one or the other. *All* SNMP applications
will need to call "init_snmp", and those acting as an agent would
need to call "init_agent" as well.
However, I'm less convinced that this is actually the cause of the
problem here. Having looked at the code properly, the config handlers
for the directives "engineBoots" and "oldEngineID" are part of the
main library rather than the agent, so should be being picked up when
you call "init_snmp" (which then calls "init_snmpv3", which is where
these handlers are registered).
So bottom line is that I *don't* think you need to call "init_agent"
for a trap handler.
What I don't understand is why your application doesn't pick up
these config tokens?
Dave
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Net-snmp-users mailing list
[EMAIL PROTECTED]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
