2010/10/16 maap maap <[email protected]>: > I was so disapointed when discovered that default net-snmp lmsensors > module uses single index for all sensor's entries, > even they are placed in different oid tables.
Could you perhaps describe why this is a problem? You have four separate tables, each of which uses a unique integer index value. What difference does it make whether these four indexes overlap or not? One advantage of keeping the current arrangement is that it paves the way for possibly implementing the IETF standard MIB for monitoring sensors (ENTITY-SENSOR-MIB) which uses a single table. If the four Net-SNMP-specific tables used independent index values, then we'd need to introduce some way of merging them for use in the Entity Sensor MIB. I'm struggling to see the advantages of your patch. Dave ------------------------------------------------------------------------------ Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
