Re: ntpdate from cron -- DON'T DO THAT! - more
On Sat, 21 Dec 2002, Bill Moseley wrote:
> At 06:51 PM 12/21/02 -0500, N. Thomas wrote:
...
> 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
sounds like you need to fix your dns ?? ( at least it found one )
( and/or hardcode it ( the ntpservers in /etc/hosts ) for quickie tests )
iirc, ntpd will not sync if you're more than 1000 seconds off... ntpdate
will resync... but you will need to resync your hwclock to the sw clock
more ntp docs, testing commands, client's ntp.conf, server's ntp.conf
http://www.linux-consulting.com/NTP
have fun
alvin
Reply to: