<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> If I adjust the timeout value to 35, I see following: <tt>add-timer: ID=1 30000 revise-timer!: ID=1 30000 revise-timer!: ID=1 86400000 add-timer: ID=2 86400000 revise-timer!: ID=2 172800000.0 revise-timer!: ID=2 172800000.0 add-timer: ID=3 30000 1 adjust-timeout! 1 35 revise-timer!: ID=3 259200000.0 revise-timer!: ID=3 35000 ALARM: id=3 add-timer: ID=4 0 ALARM: id=4 ALARM: id=3 </tt> It follows, that revise-timer adds an other alarm event. I think the expire-seconds part of the timer struct should be checked for expire before removing the continuation(?) from the hash table. Am I missing something else? --hans Matt Jadud schreef: <blockquote cite="mid:cf093f420706290223x7ffa312q3a6ed87b7955edae@mail.gmail.com" type="cite">I usually find that I answer most of my questions after asking them on the list. It's good to see others using the list for the same purpose... asking a question, answering it themselves, and then having the same forehead-slapping revelations that I do... :D Cheers, M On 6/29/07, Hans Oesterholt-Dijkema <a class="moz-txt-link-rfc2396E" href="mailto:hdnews@gawab.com"><hdnews@gawab.com></a> wrote: <blockquote type="cite">  I'm such a birdbrain,  adjust-timeout! has to be in the function given to send/supend of course!  Thanks anyway! </blockquote> </blockquote> </body> </html>