[hobbit] large system time change freezes hobbit client

[Hubbard, Greg L]

Wonder how "sleep" works?  It may take current time, add 300 seconds,
and then make a system call for an interrupt when that time arrives.  So
if you go BACK in time, the wait is a lot longer.  If you go forward in
time, the interrupt may not be delivered because it occurs in the past,
unless sleep is smart enough to return immediately when it detects time
travel.

GLH 

-----Original Message-----
From: Daniel Bourque [mailto:dbourque at weatherdata.com] 
Sent: Wednesday, June 13, 2007 2:32 PM
To: hobbit at hswn.dk
Subject: [hobbit] large system time change freezes hobbit client

Hi,

    I noticed that a large clock change tends to stop the hobbit client
from sending status messages to the server. For example, if a system
boots with the wrong time, I get cpu alerts, I go restart ntpd on it,
then I won't get anymore status until I restart hobbit-client on that
system...

    Is clientlaunch trying to keep track of the current time to
determine when to launch hobbit-client.sh, instead of just sleeping 5
minutes ( default ) in between each invocations ?

Thanks

-Dan

To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe at hswn.dk