Re: Use of Single Session API and --enable-reentrant parameter
Dave Shield <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <[email protected]> |
On 13 November 2010 21:34, Daniel D Streetman <[email protected]> wrote: > When using the Single Session API as described in the README.thread, > there is no need for net-snmp to be built with the "--enable-reentrant" parameter > (to the configure script), correct? I'm not sure that is a safe assumption, no. > The "--enable-reentrant" parameter looks like it enables locking that is not > needed for Single Session API use, but I wanted to confirm that. The main effect of the reentrant flag is to enable the methods 'snmp_res_lock' and 'snmp_res_unlock'. This is only used in the file snmplib/snmp_api.c, and appears in two basic forms: a) protecting the "Sessions" list (which is not relevant to the SS-API, correct) b) protecting the 'snmp_get_next_XXXid' routines (which are called for pretty much all SNMP applications) You'd *probably* be OK omitting the reentrant support, but it's probably not worth the risk. Dave ------------------------------------------------------------------------------ Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev _______________________________________________ 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