The way I see it, there can be no hardware related problems to cause this
problem (and this problem only). The time is kept totally independant of the
RTC, and it also seems that the RTC has a drift, but does not have this
problem.
Being as it is that I remeber some complaints about clock inacuracies in the
past, I am given to suspect that we are dealing with a kernel bug here.
Anyone cares to comment?
Shachar
> while date >> /tmp/time_track.log ; do
> sleep 60
> done
>
> was my first attempt.
>
> From there I know that time is changes at 4:01 AM to 3:01 AM.
>
> However, there was no sign of any process that changed its time!!>
>
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
