Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Leap second reminder

  • From: Gerry Boudreaux
  • Date: Sat Dec 31 14:50:15 2005

On Dec 31, 2005, at 11:58 AM, Kevin Day wrote:

Just a reminder, at midnight UTC there's a leap second added to most time systems.

Some time systems will stop the clock at 23:59:59.999999 for 1 second, some will display 23:59:60 for a second.

Since the last leap second (1998), "leap second aware" time keeping systems(NTP, GPS, etc) have become much more prevalent, so it's much more likely this time that applications and NTP sync'ed devices will see a leap second happen(rather than have them manually corrected later, or not corrected at all). But, I'm not too sure how well everyone has tested applications and devices for how they handle the clock stopping for a second OR an "invalid" time of 23:59:60.

If anyone sees anything die at 00:00:00UTC I'd be interested to know.

-- Kevin
My Juniper seems to be aware:

xxx@juniper> show ntp status
status=4694 leap_add_sec, sync_ntp, 9 events, event_peer/strat_chg,
version="ntpd 4.1.0-a Thu Jul 14 23:46:40 GMT 2005 (1)",
processor="i386", system="JUNOS7.3R1.5", leap=01, stratum=3,
precision=-30, rootdelay=40.669, rootdispersion=49.522, peer=35302,,
reftime=c7615c1c.65f78359  Sat, Dec 31 2005 13:35:56.398, poll=10,
clock=c7615d8e.d66d698f  Sat, Dec 31 2005 13:42:06.837, state=4,
offset=-2.649, frequency=73.810, jitter=5.194, stability=0.024

note the leap=01 and leap_add_sec

Discussion Communities

About Merit | Services | Network | Resources & Support | Network Research
News | Events | Contact | Site Map | Merit Network Home

Merit Network, Inc.