Re: ntpdate from cron -- DON'T DO THAT!
At 06:51 PM 12/21/02 -0500, N. Thomas wrote:
>* Sonny Kupka <sonny@nothnbut.net> [2002-12-21 10:46:12 -0600]:
>> I have ntpdate installed on woody.. and it's not automagically keeping my
>> system in sync..
>
>Contrary to what you may have heard, ntpdate does not keep your system
>clock synced. Also ignore the foolish recommendations to run ntpdate
>from a cron job.
Ok, I don't want to run ntpdate from cron, but ntpd isn't working for me --
well, at least on one machine installed on a pppoe connection (my other
machines on static IPs with the same ntpd config seem to work fine).
What happens is I ssh into the machine on the pppoe connection and it's an
hour or so slow. I'm not sure of the cause. The logs are saying that it
can't reach the hosts I've listed (which are the same as in other machines).
So maybe ntpd is giving up and never trying again.
If that's the case is there a way to tell it to continue to try?
The other possibility, brought up by someone on this list, is that that
machine is used for burning CDs and that may cause the clock to get slow.
I have not check this, though.
Anyway, here's all the logs I have:
$ fgrep ntp daemon.log.0 daemon.log | tail -10
daemon.log:Dec 16 02:20:12 burn ntpd[299]: ntpd 4.1.0 Mon Mar 25 23:39:47 UTC 2002 (2)
daemon.log:Dec 16 02:20:12 burn ntpd[299]: signal_no_reset: signal 13 had flags 4000000
daemon.log:Dec 16 02:20:12 burn ntpd[299]: precision = 12 usec
daemon.log:Dec 16 02:20:12 burn ntpd[299]: kernel time discipline status 0040
daemon.log:Dec 16 02:20:12 burn ntpd[299]: frequency initialized 13.154 from /var/lib/ntp/ntp.drift
daemon.log:Dec 16 02:20:12 burn ntpd[307]: signal_no_reset: signal 17 had flags 4000000
daemon.log:Dec 16 02:20:14 burn ntpd_initres[307]: couldn't resolve `ntp1.cmc.ec.gc.ca', giving up on it
daemon.log:Dec 16 02:20:14 burn ntpd_initres[307]: couldn't resolve `clock.netcetera.dk', giving up on it
daemon.log:Dec 16 02:20:14 burn ntpd_initres[307]: couldn't resolve `ntp1.mainecoon.com', giving up on it
daemon.log:Dec 21 14:30:29 burn ntpdate[6612]: step time server 63.192.96.2 offset 3203.797781 sec
--
Bill Moseley
mailto:moseley@hank.org
Reply to: