2009/12/15 Bart Van Assche <bart.vanass...@gmail.com>: > 2009/12/15 Jordi Gutiérrez Hermoso <jord...@gmail.com> >> >> 2009/12/15 Bart Van Assche <bart.vanass...@gmail.com>: >> > Please have a look at the mib2c tool. Once you have written a MIB >> > for the OIDs that you are already using, this tool is able to >> > convert your MIB into template code in which you can easily >> > insert your existing C code. >> >> There is one thing I don't understand about this approach. My MIB can >> change at runtime. How should that be handled? > > Can you explain further what you mean with a MIB that changes at runtime ?
I'll repeat my apology if this doesn't make sense because I don't fully understand what I'm doing. Please correct any obvious mistakes in what I'm saying. Our MIB has information about what modules are available in our application and what information they should respond to. However, our modules are largely independent between each other and communicate with standard network protocols. Should our customers at any time wish more or less functionality from our product, we can add or remove modules, and our MIB has to change to reflect this. How should a subagent handle this? At present, we have scripts that add to snmpd.conf whatever new OIDs we need, and we map the OIDs to their values with "extend" commands and the external application we've written. ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
