On Mon, 26 Sep 2005 13:15:16 +0100 Dave wrote: DS> On Fri, 2005-09-23 at 10:59 -0400, Robert Story wrote: DS> > Looking at the code, it looks like it will run DS> > every 5 minutes from the last time it was run. Thus, DS> > each time the agent is busy when the timer expires, DS> > it will drift a little. DS> DS> I've been thinking about this. DS> What would be the disadvantages of calculating DS> the next alarm time *before* invoking the callback DS> routine (rather than afterwards)?
As far as backwards compatability, it could cause things to be called more sooner than desired. eg a task that registers for every 30 seconds but takes 5 seconds to complete would be called after 25 seconds, instead of the expected (based on current behavior) 30. I've no objections to such a mode, but I'd say it should be an option (defaulting to the current behavior, for now). DS> That would allow a more regular invocation of DS> such routines, without this sort of drift. <nitpick>well, it wouldn't elminate it, but it would greatly reduce it.</nitpick> -- Robert Story; NET-SNMP Junkie Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp> Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-users> You are lost in a twisty maze of little standards, all different. ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
