Hi Robert, Unfortunately, this is still a problem in 5.3.1. A little bit debug convinced me this was deeper than what I could afford to spend time on.
I neither used 5.3.2 nor 5.4.1, so don't know if it is reproducible in newer versions than 5.3.1. I am glad it finally got your attention ;-) Please fix it. Best regards, Emi -----Original Message----- From: Robert Story [mailto:[EMAIL PROTECTED] Sent: Monday, October 15, 2007 10:06 AM To: Emi Yanagi Cc: [email protected] Subject: Re: When there is "no instance" object in a table, snmpgetnext skip the rest of the objects in the table and search for the next table On Thu, 6 Sep 2007 08:30:54 -0700 Emi wrote: EY> I am using 5.3.1, the implementation agent/mibgroup/notification-log-mib EY> is provided in 5.3.1. Since transport is NULL, EY> COLUMN_NLMLOGENGINETADDRESS and COLUMN_NLMLOGENGINETDOMAIN are NULL. EY> However, COLUMN_NLMLOGNOTIFICATIONID is not NULL, but getnext would skip EY> it because of the two NULL objects before it. This is the problem I am EY> reporting. Did this ever get resolved? If not, is it producible in 5.3.2? 5.4.1? ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
