I think we have 2 issues: one that we have limited resources and the other that even when we have the resources, we are hitting the 2048 byte limit set when creating the response buffer in _sess_async_send() in snmplib\snmp_api.c . As far as I can tell, in the latter case we just time out the request rather than attempt to send a too big (or any other) error response. Is this the correct behavior?
Adam. > -----Original Message----- > From: Wes Hardaker [mailto:[email protected]] > Sent: Thursday, August 18, 2011 4:51 PM > To: Lewis Adam-VNQM87 > Cc: [email protected] > Subject: Re: consistent response handling for running out of resources > > >>>>> On Thu, 11 Aug 2011 12:33:43 +0100, "Lewis Adam-VNQM87" > <[email protected]> said: > > LA> As I have mentioned, we do have an embedded system with limited > LA> resources and it would be interesting to know how unix-style agents > cope > LA> with the same sort of test. > > RFC3416 has this to say: > > Otherwise, an alternate Response-PDU is generated. This alternate > Response-PDU is formatted with the same value in its request-id > field > as the received GetRequest-PDU, with the value of its error-status > field set to "tooBig", the value of its error-index field set to > zero, and an empty variable-bindings field. > > -- > Wes Hardaker > Please mail all replies to [email protected] ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
