Hello Koen,
Friday, December 30, 2005, 2:30:02 AM, you wrote:
>>Highly likely it has a Lot to do with it :-) Maybe the master time
>>server had `date` run manually, or otherwise shifted, or came back
>>on net after an outage, & the systems noticed drifted time & corrected etc.
>> man ntpd
>
Julian H. Stacey wrote:
PS. Not sure if this have anything to do with it (the message mentions CPU
time, not the clock), but I'm running a ntp daemon, to synchronize time...
Highly likely it has a Lot to do with it :-) Maybe the master time
server had `date` run manually, or otherwise shi
Hello Julian,
Thursday, December 29, 2005, 4:39:55 PM, you wrote:
> Highly likely it has a Lot to do with it :-) Maybe the master time
> server had `date` run manually, or otherwise shifted, or came back
> on net after an outage, & the systems noticed drifted time & corrected etc.
> man n
> PS. Not sure if this have anything to do with it (the message mentions CPU
> time, not the clock), but I'm running a ntp daemon, to synchronize time...
Highly likely it has a Lot to do with it :-) Maybe the master time
server had `date` run manually, or otherwise shifted, or came back
on net aft
