nger than a million years.
--
Miroslav Lichvar
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
https://pairlist6.pair.net/mailman/listinfo/leapsecs
anging during the leap smear.
https://developers.redhat.com/blog/2015/06/01/five-different-ways-handle-leap-seconds-ntp/
--
Miroslav Lichvar
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
https://pairlist6.pair.net/mailman/listinfo/leapsecs
to slow down or speed up Earth enough for
UTC to require more than two leap seconds per year and how quickly can
it be released without destroying those that care about UTC following
UT1?
--
Miroslav Lichvar
___
LEAPSECS mailing list
LEAPSECS@leapseco
pool DNS had some issues around July 1st, so it might
> be worth checking if anyone else recorded anything unusual.
In my logs I see only one server that was announcing a leap second on
June 30th. It was two the month before that and about 70 on January
31th 2017.
--
Miroslav Lichvar
I'm with what the
solution should be.
--
Miroslav Lichvar
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
https://pairlist6.pair.net/mailman/listinfo/leapsecs
. The
clock on the first one was corrected by stepping, the second one by
fast slewing.
https://mlichvar.fedorapeople.org/leap2015/clock_step.gif
https://mlichvar.fedorapeople.org/leap2015/clock_slew.gif
--
Miroslav Lichvar
___
LEAPSECS mailing list
LEAPSECS
synchronized by
NTP/PTP using the right/UTC timezone and display 23:59:60.
https://github.com/mlichvar/leapclock
It should work on Linux and possibly other systems where the kernel
steps the clock back when it gets to 00:00:00.
--
Miroslav Lichvar
closely a
server that smears leap second in just two hours.
Anyway, from the article it's not clear to me if they will make a leap
smear on NTP servers or precompensate the clocks locally be slewing.
--
Miroslav Lichvar
___
LEAPSECS mailing list
LEAPSECS
