Re: Problem in explicit call to run_alarams function from "trap

On 11/04/07, bhushan <sonawanebhushan@gmail.com> wrote:
> In my application snmpd will stop at any point in time & start again so for
> my subagent it is
> difficult to know that snmpd stop for same time & started again

That's already handled by the agentx subagent framework.
See the directive 'agentXPingInterval' in snmpd.conf(5)



> so my question is calling "run_alarms" explicitly from subagent code will
> be safe or not ?

It should be OK, since it's part of the normal operation of an agent or
subagent. If you use the Net-SNMP 'receive()' routine as the event
loop, or call 'agent_check_and_process()' to handle incoming PDUs,
then these already call 'run_alarms()' anyway.

If there's nothing due to be run, then run_alarms() will return without
doing anything, so there shouldn't be any problem in calling it at other
times too. It might waste a little bit of processing time, but that should
be all.

Dave

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?p...rge&CID=DEVDEV
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders