From: Dale Martenson <dmartenson@...>
Date: 2004-06-11T09:01:59+09:00
Subject: Re: The dangers of sleeping ...

> -----Original Message-----
> From: Ben Giddings [mailto:bg-rubytalk@infofiend.com]
> Sent: Thursday, June 10, 2004 6:00 PM
> 
> Dale Martenson wrote:
> > This problem came up as part of a large ruby server 
> application where an
> > operator noticed the time on the server was way off and set 
> the clock back a
> > couple of hours to correct the problem. The system locked 
> up. Threads using
> > the sleep function never woke up. 
> 
> There's your problem.

...

> This doesn't mean this isn't a bug, and it doesn't mean that software 
> shouldn't be written with the possibility of this happening 
> in mind, but 
> it's really the fault of the person running the system.

I guess when I think of sleeping. I don't see the relationship between
sleeping for a particular length of time and what the clock says. This may
be since I work with a lot embedded systems where tick counts are used to
for timing events. Date and time information may or may not be available.

I just thought it was odd that it wasn't accounted for and that its behavior
varied depending on if it was in a thread or not.