On 24 February 2010 11:09, Tanisha Kashyap <tanisha.kash...@aricent.com> wrote: > I have defined the following cases in my code for the SET REQUEST: > > MODE_SET_RESERVE1 > MODE_SET_RESERVE2 > MODE_SET_FREE -> does nothing > MODE_SET_ACTION > MODE_SET_COMMIT -> does nothing > MODE_SET_UNDO -> does nothing > > The function that is invoked multiple times is defined under the > MODE_SET_ACTION case. > > Since I have defined all the cases for the Set request so the function under > MODE_SET_ACTION > case shouldn't be invoked more than once. > > Is my thought correct?
That sounds right, yes. If your routine is *only* being called multiple times for the ACTION pass, and not for the earlier ones, then that sounds like an issue with the agent processing. (Since a re-sent SET request would start again with RESERVE1) That sounds a very odd situation, though - since I'd expect to have heard of such problems before now. What version of the agent are you using? Does this happen for all SET requests, or just particular OIDs? Dave ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
