Carlos E. R. wrote:
On 2017-01-06 10:44, Per Jessen wrote:
Per Jessen wrote:
Carlos E. R. wrote:
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.
Well, I've installed Leap421 on a desktop, I've set the time to 23:50 31/12/2016. There is no ntp running nor installed, how do I now tell if the leap second is introduced or not?
I tried with 42.2 the same thing, and didn't see anything in the log.
One way to check is write a little script that loops and print the time to a file (with milliseconds precision at least), then sleeps a second. I used that trick ages ago to test for an issue I had.
Well, the test worked - without someone prodding it, as I was certain it couldn't, the kernel knows nothing about any leap seconds. Just now, I set system time to 31 Dec 23:50 UTC, rebooted, let ntp sync to LOCAL: /var/log/ntp: 1 Jan 00:50:53 ntpd[1491]: 0.0.0.0 c01d 0d kern kernel time sync enabled 1 Jan 00:50:53 ntpd[1491]: 0.0.0.0 c012 02 freq_set kernel 0.000 PPM 1 Jan 00:50:53 ntpd[1491]: 0.0.0.0 c016 06 restart 1 Jan 00:56:14 ntpd[1491]: 0.0.0.0 c515 05 clock_sync office31:~ # ntpq -pn remote refid st t when poll reach delay offset jitter ============================================================================== *127.127.1.0 .LOCL. 10 l 52 64 377 0.000 0.000 0.000 No mention of any leap seconds in /var/log/messages nor /var/log/ntp. -- Per Jessen, Zürich (-7.6°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org