>>>>> On Wed, 14 Jun 2006 15:29:25 +0100, Dave Shield <[EMAIL PROTECTED]> said:
AV> 2) Is there any concept of caching out the cached data if for some reason AV> I did not receive set for all mandatory columns I am expecting. This AV> might happen let say col1 and col2 is set and came in one PDU, however, AV> for some reason col3 in second PDU did not arrive at the agent. AV> ( say manager got disconnected), then in that case will that cached data AV> be flushed out by the subagent. >> >> This could easily be done by setting a timer callback when the row is >> created/modified. >> Dave> A strict reading of the semantic of RowStatus implies that this Dave> is exactly what ought to happen. I don't believe that any of Dave> the agents helpers implements this by default (although I'm Dave> somewhat out of touch with recent developments). But as Robert Dave> says, it really just needs a timer to trigger a callback to Dave> remove the internal representation of the row. (And remembering Dave> to stop/remove the timer when the row is activated!) Actually, a timer should be started on any row where the rowstatus value is not-in-service, not just ones that are not-in-service because of a createAndWait... Rows that were active and then changed to not-in-service are technically supposed to be auto-deleted as well. -- Wes Hardaker Sparta, Inc. _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
