Bug#252289: general: system clock goes chaoticly causing system breakdown
On Thu, 03 Jun 2004, Frank Küster wrote:
Antos Andras <antos@szit.bme.hu> wrote:
On one of my Debian boxes, the system clock goes chaoticly. Logging in
locally, the system clock goes too fast, by up to 150 sec in an hour.
After a while it stops or it goes around on a loop of 3-4 secs...
Have you any programs installed that are involved with setting the
system clock? chrony, adjtimex, ntpdate and ntp are candidates that come
to my mind, but there may be more, some have their own daemons, some
work with cron jobs.
Only ntpdate is installed, which sets date only once at boot in
/etc/init.d/ntpdate.
All these start happening only when I am logged in locally (I think).
It would be good to find that out. If your computer has access to an
external clock, you could check this regularly and write it into a log
file, e.g. with something like
while true; do
links -dump www.uhrzeit.org |grep "Die Uhrzeit" >> /var/log/mytime.log
date >> /var/log/mytime.log
wait $appropriate_time
done
or a cron job.
:) I did almost the same putting this script into /etc/cron.hourly/ :
. /etc/default/ntpdate
{ date; hwclock -r; ntpdate -q ${NTPSERVERS:-pool.ntp.org}; }\
>>/home/antos/time.log
In the logfile I see that the ntpdate offset increases only 0.08 or 0.16
seconds an hour while I am not logged in, but it can be anything up to 150
seconds an hour while I am logged in. (Shell I send the logfile?)
Andras
Reply to: