Excellent news .... 

So based on your response, it seems like I can set "processed = 1" in the 
"_object_lookup()" routine at the same time I set "req->requestvb->type = 
SNMP_NOSUCHINSTANCE".    This seems to be a more general solution which you 
prefer.  My check then could simply check "processed" instead of the 
"NOSUCHINSTANCE" return value directly .... correct.

Hey, one more thing, which error codes are considered "hard" errors?

Thanks for all your help.



Robert Story <[EMAIL PROTECTED]> wrote: On Wed, 20 Jun 2007 12:50:17 -0700 
(PDT) Need wrote:
NH> I looked around the code a bit and noticed some things which might explain 
the reason for this occurring.  In the 
"_mfd_ocStbHostAnalogVideoTable_object_lookup()" routine the following code 
exists:
NH> 
NH>         for (req=requests; req;  req=req->next)
NH>            req->requestvb->type = SNMP_NOSUCHINSTANCE;

I forgot we were setting this directly, so processed wasn't set.

NH> 2)  As a result of (1) above, I decided to try the following code in the 
"_mfd_ocStbHostAnalogVideoTable_get_values()" routine which checks to check for 
the "requestvb->type" field instead:
NH> 
NH>    if (requests->requestvb->type == SNMP_NOSUCHINSTANCE)
NH>         continue;

It works, so you can leave it. But if I get around to updating the MfD code,
I'll be using processed as well...


       
---------------------------------
Luggage? GPS? Comic books? 
Check out fitting  gifts for grads at Yahoo! Search.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to