Hi, This is the test result. Please advise.
root@localhost:/etc/snmp> snmpset -v2c -c NETMAN 127.0.0.1 .1.3.6.1.6.3.12.1.2.1.9.0.25 i 5 SNMP-TARGET-MIB::snmpTargetAddrRowStatus.'..' = INTEGER: createAndWait(5) root@localhost:/etc/snmp> snmpset -v2c -c NETMAN 127.0.0.1 .1.3.6.1.6.3.12.1.2.1.9.0.25.1 i 5 SNMP-TARGET-MIB::snmpTargetAddrRowStatus.'...' = INTEGER: createAndWait(5) root@localhost:/etc/snmp> snmpset -v2c -c NETMAN 127.0.0.1 .1.3.6.1.6.3.12.1.2.1.9.0.25.1.1 i 5 SNMP-TARGET-MIB::snmpTargetAddrRowStatus.'....' = INTEGER: createAndWait(5) root@localhost:/etc/snmp> snmpset -v2c -c NETMAN 127.0.0.1 .1.3.6.1.6.3.12.1.2.1.9.0.25.1.1.1 i 5 SNMP-TARGET-MIB::snmpTargetAddrRowStatus.'.....' = INTEGER: createAndWait(5) root@localhost:/etc/snmp> snmpset -v2c -c NETMAN 127.0.0.1 .1.3.6.1.6.3.12.1.2.1.9.1.25.1.1.1 i 5 SNMP-TARGET-MIB::snmpTargetAddrRowStatus.'.....' = INTEGER: createAndWait(5) root@localhost:/etc/snmp> snmpset -v2c -c NETMAN 127.0.0.1 .1.3.6.1.6.3.12.1.2.1.9.1.25.1.1 i 5 SNMP-TARGET-MIB::snmpTargetAddrRowStatus.'....' = INTEGER: createAndWait(5) root@localhost:/etc/snmp> snmpset -v2c -c NETMAN 127.0.0.1 .1.3.6.1.6.3.12.1.2.1.9.1.25.1 i 5 SNMP-TARGET-MIB::snmpTargetAddrRowStatus.'...' = INTEGER: createAndWait(5) root@localhost:/etc/snmp> snmpset -v2c -c NETMAN 127.0.0.1 .1.3.6.1.6.3.12.1.2.1.9.1.25 i 5 SNMP-TARGET-MIB::snmpTargetAddrRowStatus.'..' = INTEGER: createAndWait(5) root@localhost:/etc/snmp> snmpset -v2c -c NETMAN 127.0.0.1 .1.3.6.1.6.3.12.1.2.1.9.1.26 i 5 SNMP-TARGET-MIB::snmpTargetAddrRowStatus.'..' = INTEGER: createAndWait(5) root@localhost:/etc/snmp> snmpset -v2c -c NETMAN 127.0.0.1 .1.3.6.1.6.3.12.1.2.1.9.1.27 i 5 SNMP-TARGET-MIB::snmpTargetAddrRowStatus.'..' = INTEGER: createAndWait(5) root@localhost:/etc/snmp> snmpset -v2c -c NETMAN 127.0.0.1 .1.3.6.1.6.3.12.1.2.1.9.6.2 i 5 SNMP-TARGET-MIB::snmpTargetAddrRowStatus.'..' = INTEGER: createAndWait(5) root@localhost:/etc/snmp> snmpwalk -v2c -c NETMAN 127.0.0.1 .1.3.6.1.6.3.12.1.2.1.9 -Ofn .1.3.6.1.6.3.12.1.2.1.9.0.25 = INTEGER: notReady(3) .1.3.6.1.6.3.12.1.2.1.9.0.25.1 = INTEGER: notReady(3) .1.3.6.1.6.3.12.1.2.1.9.0.25.1.1 = INTEGER: notReady(3) .1.3.6.1.6.3.12.1.2.1.9.0.25.1.1.1 = INTEGER: notReady(3) .1.3.6.1.6.3.12.1.2.1.9.1.25 = INTEGER: notReady(3) .1.3.6.1.6.3.12.1.2.1.9.1.25.1 = INTEGER: notReady(3) .1.3.6.1.6.3.12.1.2.1.9.1.25.1.1 = INTEGER: notReady(3) .1.3.6.1.6.3.12.1.2.1.9.1.25.1.1.1 = INTEGER: notReady(3) .1.3.6.1.6.3.12.1.2.1.9.1.26 = INTEGER: notReady(3) .1.3.6.1.6.3.12.1.2.1.9.1.27 = INTEGER: notReady(3) .1.3.6.1.6.3.12.1.2.1.9.6.2 = INTEGER: notReady(3) Best Regards! zhuyj On 07/17/2013 10:23 AM, zhuyj wrote: > Any advice? > > On 07/16/2013 04:49 PM, zhuyj wrote: >> Hi, Magnus >> >> Based on your patch, I made a new patch. This patch depends on >> net-snmp5.7.2. >> I made the following modifications compared with your patch: >> 1.add strdup2 to replace strdup; >> 2.modify addToList function; >> 3.change some NUL-terminated strings to counted-strings, but not all; >> >> The patch is in the attachment. Please check it. >> >> Best Regards! >> zhuyj >> On 07/16/2013 02:14 PM, Magnus Fromreide wrote: >>> On Tue, 2013-07-16 at 10:27 +0800, zhuyj wrote: >>>> Thanks for your help! >>>> I agree with you. It is a big task to replace all the NUL-terminated >>>> string with counted-string. >>>> Now I have a patch that can fix this. Would you like to merge this >>>> patch in master of net-snmp? >>> If you send out the patch then I will look at it. >>> >>> /MF >>> >>> >>> >> > > ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
