On Thu, 2005-04-14 at 22:25, Robert Story wrote:
> Doesn't setting SNMP_FLAGS_DONT_PROBE in the session flags work? That should
> prevent the probe and allow a valid session struct to be returned.
Possibly, but it still feels like an unnecessary step.
With the old v4 distributions (and even with v5, given a configure
choice of SNMPv1 or SNMPv2c as the default version), then
snmp_sess_init( &sess );
ss1 = snmp_open( &sess );
ss2 = snmp_open( &sess );
would work, and you could set all of the configuration for ss1
and ss2 sessions separately.
With a v5-SNMPv3 default, then the same code fails when talking
to a community-only agent.
Let's take a step back - what's the purpose behind sending the
probe at this point (opening the session) rather than later on
(when it's actually used) ?
What would be the implications of defaulting to "DONT_PROBE"?
Alternatively, what would be the implications of probing, but
returning a session structure anyway, even if the probe failed?
Dave
[I can't believe that I'm arguing to change this, having already
documented this behaviour in the client-side programming chapter!]
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
