[ntp:questions] Another invalid leap second

Chris Adams cma at cmadams.net
Tue Jul 2 22:55:02 UTC 2013


I have a Linux (Fedora 18) system running ntp-4.2.6p5-8.fc18.x86_64.  I
have a GPS receiver connected (old Trimble SVeeSix in TSIP mode).  I
have some pool servers plus my ISPs servers configured.  After some
discussion on a mailing list, I checked, and I got a leap second Sunday.
I see this in my log (my local time is CDT, UTC-0500):

Jun 30 03:03:04 disk ntpd[1150]: 0.0.0.0 411a 0a leap_disarmed
Jun 30 03:04:40 disk ntpd[1150]: 0.0.0.0 412a 0a leap_disarmed
Jun 30 18:59:59 disk kernel: [2575160.498722] Clock: inserting leap second 23:59:60 UTC
Jun 30 19:05:48 disk ntpd[1150]: 0.0.0.0 4118 08 no_sys_peer
Jun 30 19:06:23 disk ntpd[1150]: 0.0.0.0 4413 03 spike_detect +0.996853 s
Jun 30 19:15:26 disk ntpd[1150]: 0.0.0.0 441c 0c clock_step +0.999959 s
Jun 30 19:15:26 disk ntpd[1150]: 0.0.0.0 4415 05 clock_sync
Jun 30 19:15:27 disk ntpd[1150]: 0.0.0.0 c418 08 no_sys_peer

Where did the leap second come from?
-- 
Chris Adams <cma at cmadams.net>



More information about the questions mailing list