2008/7/1 <[EMAIL PROTECTED]>: > I agree to your point that we need to take lock on every place of my mib > module > (whose code is generated by mib2c) which access the CONTAINER
Not just your code - you will need to look at any relevant helpers as well. Remember that the Net-SNMP agent is not designed for multi-threaded operation, so you cannot assume that *any* code is thread-safe. > But could u just let me know that do in any case locking to be done in > netsnmp code and api's. No - I cannot provide any more assistance on this issue. You are taking the agent outside the scope of its current design, so you are in uncharted territory. I am already committing more time than I can realistically spare to answering questions on this list. Adding mutli-threaded support (even in a very restricted way) is a non-trivial task, and one that I have no experience of. If you feel that your coding experience is up to this, then it would be very useful to hear of your experiences, so that others can learn from them. If you suspect that this may be beyond your capabilities, then you should probably consider hiring a consultant to do the work for you. But you cannot reasonably expect us to provide this sort of consultancy for free. You are the one that wants multi-threaded support. The onus is therefore on you to provide it. Dave ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
