Hello, I'm running the latest portable OpenNTPD on a Debian box, but it's just not keeping time. When I first start it, just executing ntpd, it sets the time correctly, but then starts diverging, after a couple of weeks, like this (this machine is currently one hour and a half ahead):
sh-3.00$ sudo tail /var/log/daemon.log [...] Dec 15 21:55:57 localhost ntpd[24843]: adjusting local clock by -6431.804472s Dec 15 21:55:57 localhost ntpd[24843]: adjtime failed: Invalid argument Dec 15 21:58:45 localhost ntpd[24844]: peer 200.218.160.160 now valid Dec 15 21:59:09 localhost ntpd[24843]: adjusting local clock by -6432.906307s Dec 15 21:59:09 localhost ntpd[24843]: adjtime failed: Invalid argument Dec 15 21:59:19 localhost ntpd[24844]: peer 80.74.132.178 now valid Dec 15 21:59:38 localhost ntpd[24844]: peer 202.173.190.30 now valid Dec 15 22:03:11 localhost ntpd[24844]: peer 216.194.70.2 now valid Dec 15 22:04:00 localhost ntpd[24843]: adjusting local clock by -6433.975776s Dec 15 22:04:00 localhost ntpd[24843]: adjtime failed: Invalid argument Dec 15 22:04:13 localhost ntpd[24844]: peer 62.112.194.60 now invalid Dec 15 22:08:10 localhost ntpd[24843]: adjusting local clock by -6435.087634s Dec 15 22:08:10 localhost ntpd[24843]: adjtime failed: Invalid argument Dec 15 22:11:38 localhost ntpd[24843]: adjusting local clock by -6436.039326s Dec 15 22:11:38 localhost ntpd[24843]: adjtime failed: Invalid argument Dec 15 22:14:20 localhost ntpd[24843]: adjusting local clock by -6437.093983s Dec 15 22:14:20 localhost ntpd[24843]: adjtime failed: Invalid argument Dec 15 22:15:11 localhost ntpd[24844]: peer 62.112.194.60 now valid Dec 15 22:16:10 localhost ntpd[24844]: peer 62.52.109.76 now invalid Dec 15 22:17:19 localhost ntpd[24843]: adjusting local clock by -6437.998041s Dec 15 22:17:19 localhost ntpd[24843]: adjtime failed: Invalid argument Dec 15 22:21:32 localhost ntpd[24843]: adjusting local clock by -6438.912244s Dec 15 22:21:32 localhost ntpd[24843]: adjtime failed: Invalid argument Dec 15 22:22:57 localhost ntpd[24844]: peer 216.194.70.2 now invalid [...] I seem to have understood that at a certain point, when the time difference is too big, the adjtime call can no longer be used, but how does it get to this point in the first place? I would really like to have this solved as I am running mythtv on this machine, and with a timekeeper like this I'll never be able to record the one programme I'd actually like to watch :-). Thanks in advance, Jakob.
