On 2006-05-05, Marc 'BlackJack' Rintsch <[EMAIL PROTECTED]> wrote: > In <[EMAIL PROTECTED]>, OlafMeding > wrote: > >>> IIRC it was something like an NTP daemon that caused the clock >>> to "jump" a little and (Window's) sleep was confused. >> >> The problem is not a "jump" but a permanet lockup of the sleep >> statement. > > The "jump" of the system clock might confuse the systems > `sleep` implementation.
I wouldn't be a bit surprised if MS write code to wake up a task when the currentTime == task.wakeupTime instead of when currentTime >= task.wakeupTime. If the system time jumps past the "wakeup" point without ever passing through it, the task sleeps forever. Microsoft's bungling of simple things like timer ticks is legend in some circles: http://www.embedded.com/showArticle.jhtml?articleID=57703680 http://www.embedded.com/showArticle.jhtml?articleID=159902113 -- Grant Edwards grante Yow! I'm young... I'm at HEALTHY... I can HIKE visi.com THRU CAPT GROGAN'S LUMBAR REGIONS! -- http://mail.python.org/mailman/listinfo/python-list
