Carlos E. R. wrote:
But my read of the logs disproves this theory. My kernel did know about the leap second, and it was the kernel who informed ntp, not the other way round.
You are misreading the log, Carlos. The log message is written by ntpd after calling ntp_adjtime(). This call returns a condition or code, and ntpd just logs it, that's all.
The leap seconds are builtin inside the kernel.
Common sense says that simply isn't possible. My 1[123]1.x systems could not possibly know about the most recent leap second, their kernels pre-date the IERS Bulletin C 52 from July 2016 by quite a bit - yet surprisingly, they found out about the leap second. https://hpiers.obspm.fr/iers/bul/bulc/bulletinc.52
This can be proved by running an isolated test machine without ntp, and setting the time on it to Dec 31th, see what happens in the log. My bet is it adds the leap second.
I'll be happy to test that tomorrow. -- Per Jessen, Zürich (-2.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org