On 23 November 2011 08:02, <[email protected]> wrote:
> I used to understand whether the “snmp_async_send” was successful or not, by
> looking at its return value.
>
> Now it returns a “non-zero value” regardless of success or failure.
Think about what "failure" means here.
For an asynchronous request - failure basically means
"I couldn't send the request"
typically because the destination wasn't recognised.
As long as the client side can construct and send the request,
this is regarded as "success" - whether or not there is anything
actually listening at the specified destination.
If the request times out, or is rejected as malformed, or any
other form of failure - all of this will only be detected *after*
the request has been sent, and the async_send call returns.
So yes - such problems need to be checked for and handled
within the callback function.
Have a look at the "Simple_Async_Application" tutorial
on the project wiki site
(http://www.net-snmp.org/wiki/index.php/TUT:Simple_Async_Application)
Dave
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
