nanog mailing list archives
Re: REMINDER: Leap Second
From: "Mike." <the.lists () mgm51 com>
Date: Sun, 25 Jan 2015 10:19:29 -0500
On 1/25/2015 at 9:37 AM Jay Ashworth wrote: |This June 30th, 235959UTC will be followed immediately by 235960UTC. | |What will /your/ devices do? ============= I've always wondered why this is such a big issue, and why it's done as it is. In UNIX, for instance, time is measured as the number of seconds since the UNIX epoch. imo, the counting of the number of seconds should not be "adjusted", unless there's a time warp of some sort. The leap second adjustment should be in the display of the time, i.e., similar to how time zones are handled. fwiw
Current thread:
- REMINDER: Leap Second Jay Ashworth (Jan 25)
- Re: REMINDER: Leap Second Mike. (Jan 25)
- Re: REMINDER: Leap Second Karsten Elfenbein (Jan 25)
- Re: REMINDER: Leap Second Ken Chase (Jan 25)
- Re: REMINDER: Leap Second Joe Klein (Jan 25)
- Re: REMINDER: Leap Second Karsten Elfenbein (Jan 25)
- Re: REMINDER: Leap Second John Levine (Jan 25)
- Re: REMINDER: Leap Second Valdis . Kletnieks (Jan 25)
- Re: REMINDER: Leap Second Ken Chase (Jan 25)
- Re: REMINDER: Leap Second Stephen Satchell (Jan 25)
- Re: REMINDER: Leap Second Barney Wolff (Jan 25)
- Re: REMINDER: Leap Second TR Shaw (Jan 25)
- Re: REMINDER: Leap Second Barney Wolff (Jan 26)
- Re: REMINDER: Leap Second Mike. (Jan 25)
