Re: hard crash on leap second
On Wed December 31 2008, Ken Irving wrote:
> > Dec 31 18:03:01 haggis ntpdate[9521]: step time server 68.0.14.76 offset
> > -0.562385 sec
>
> I see the same as that in a machine running ntpdate. I used to mainly use
> ntpdate, but saw lots of references (though I have no citations to offer)
> recommending ntp over ntpdate, and find that it *just works" now when I set
> up a machine.
I didn't realize we had a choice..
mine looks like this:
grep ntp /var/log/syslog
Dec 31 12:35:47 paulandcilla ntpd[3701]: clock is now synced
Dec 31 12:43:39 paulandcilla ntpd[3700]: adjusting local clock by -0.176692s
Dec 31 15:41:23 paulandcilla ntpd[3701]: peer 207.5.137.134 now invalid
Dec 31 15:49:56 paulandcilla ntpd[3701]: peer 209.67.219.106 now invalid
Dec 31 15:53:50 paulandcilla ntpd[3701]: peer 64.247.17.250 now valid
Dec 31 16:00:16 paulandcilla ntpd[3701]: peer 64.247.17.250 now invalid
Dec 31 16:02:21 paulandcilla ntpd[3701]: peer 209.104.4.227 now valid
Dec 31 16:13:01 paulandcilla ntpd[3701]: peer 72.52.190.26 now valid
Dec 31 19:30:37 paulandcilla ntpd[3700]: adjusting local clock by -0.689160s
Dec 31 19:34:18 paulandcilla ntpd[3700]: adjusting local clock by -0.511293s
Dec 31 19:34:18 paulandcilla ntpd[3701]: clock is now unsynced
Dec 31 19:38:42 paulandcilla ntpd[3700]: adjusting local clock by -0.257269s
Dec 31 19:42:34 paulandcilla ntpd[3700]: adjusting local clock by -0.473127s
Dec 31 19:44:52 paulandcilla ntpd[3700]: adjusting local clock by 0.136218s
Dec 31 19:56:37 paulandcilla ntpd[3700]: adjusting local clock by -0.344708s
Dec 31 19:56:37 paulandcilla ntpd[3701]: clock is now synced
Dec 31 19:59:46 paulandcilla ntpd[3700]: adjusting local clock by -0.174025s
Dec 31 19:59:46 paulandcilla ntpd[3701]: clock is now unsynced
Dec 31 20:07:27 paulandcilla ntpd[3701]: clock is now synced
Dec 31 20:56:19 paulandcilla ntpd[3700]: adjusting local clock by -0.159575s
--
Paul Cartwright
Registered Linux user # 367800
Registered Ubuntu User #12459
Reply to: