[LEAPSECS] A standard for leap second smearing
Tom Van Baak
tvb at LeapSecond.com
Wed Sep 28 11:31:58 EDT 2016
NTP is designed to disseminate the SI second and a UTC timestamp. If you want a completely different timescale (e.g., UT1, or some smeared variant of UTC) it seems like this could be part of NTP, not some opaque hack below or above NTP so as to "fake out" ancient or hardcoded assumptions of NTP.
Is it really easier and wiser to propose a universal layer of kernel timekeeping hacks than to change how NTP works or how NTP is configured or how UTC is defined?
----- Original Message -----
From: "Stephen Colebourne" <scolebourne at joda.org>
To: "Leap Second Discussion List" <leapsecs at leapsecond.com>
Sent: Wednesday, September 28, 2016 7:40 AM
Subject: Re: [LEAPSECS] A standard for leap second smearing
> On 28 September 2016 at 14:39, Tony Finch <dot at dotat.at> wrote:
>> Steve Summit <scs+ls at eskimo.com> wrote:
>>> Me, I'd very much rather *not* add this sort of thing to (say)
>>> NTP, because NTP doesn't have a problem with leap seconds.
> This does seem true - hacking ntp feels like the wrong solution.
>> Except that every leap second is screwed up by a large proportion of NTP
> True. But there are far fewer ntp servers than installations of an OS
> kernel. So, it should be a more tractable problem to fix.
> LEAPSECS mailing list
> LEAPSECS at leapsecond.com
More information about the LEAPSECS