As always your feedback and replies are appreciated. I read AGENT.txt as well as the mail list thread you mentioned Both materials helped enforce what I was already thinking ( or fearing )
My question was not so much to do with multi-pass nature of the set operation and the need to structure the design to process it in multi pass, but rather to do with what was the best way to service the set operation in each pass, request-by-request struct or var-by-var struct. It was this last choice that was confusing but after reading the document and the thread and with few subtle hints here and there I realized that I have to make the choice how to process the operation. this email is sent as a courtesy and in the interest of being of some value to others like me and no reply is expected. Bernadette Eyre -----Original Message----- From: dave.shi...@googlemail.com on behalf of Dave Shield Sent: Fri 3/20/2009 5:44 AM To: EYRE Bernadette Cc: net-snmp-coders@lists.sourceforge.net Subject: Re: processing of the multi varbinds in one snmpset command 2009/3/19 EYRE Bernadette <bernadette.e...@alcatel-lucent.com>: > if the snmpset command line has multiple varbinds (variables) to modify for > the same table > and the same row (index), how can one ensures that all vars are processed in > one request struct? That's the reason that SET requests are processed in multiple passes. Have a look at the file AGENT.txt, for a description of one possible approach. It might also be worth searching the mailing list archives - I'm pretty sure that I've explained this sort of thing before. (a quick search throws up a thread on the -users list from 10th Feb, entitled"Parsing Get/Set Requests in Table_Handler". That looks relevant) Dave
------------------------------------------------------------------------------
_______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
