On 2017-01-03 11:42, Per Jessen wrote:
Roger Oberholtzer wrote:
At the end of 2016, my openSUSE system reported:
Clock: inserting leap second 23:59:60 UTC
I can't seem to find that one anywhere. In /var/log/ntp, I see this on some systems:
I see it in /var/log/messages: Jan 01 00:55:01 Isengard systemd[1]: Stopped User Manager for UID 0. Jan 01 00:55:01 Isengard systemd[1]: Removed slice User Slice of root. Jan 01 00:59:59 Isengard systemd[2287]: Time has been changed Jan 01 00:59:59 Isengard kernel: Clock: inserting leap second 23:59:60 UTC <====== Jan 01 00:59:59 Isengard systemd[1]: Time has been changed Jan 01 01:00:01 Isengard cron[14493]: pam_unix(crond:session): session opened for user root by (uid=0) Jan 01 01:00:01 Isengard cron[14491]: pam_unix(crond:session): session opened for user root by (uid=0) Jan 01 01:00:01 Isengard cron[14492]: pam_unix(crond:session): session opened for user root by (uid=0) Jan 01 01:00:01 Isengard systemd[1]: Created slice User Slice of root. Jan 01 01:00:01 Isengard systemd[1]: Starting User Manager for UID 0... Jan 01 01:00:01 Isengard systemd[14494]: pam_unix(systemd-user:session): session opened for user root by (uid=0) Jan 01 01:00:01 Isengard systemd[1]: Started Session 11986 of user root. Jan 01 01:00:01 Isengard systemd[1]: Started Session 11985 of user root. Jan 01 01:00:01 Isengard systemd[1]: Started Session 11987 of user root. Jan 01 01:00:01 Isengard systemd[14494]: Reached target Timers. Jan 01 01:00:01 Isengard systemd[14494]: Reached target Sockets. Jan 01 01:00:01 Isengard systemd[14494]: Reached target Paths. Jan 01 01:00:01 Isengard systemd[14494]: Reached target Basic System. Jan 01 01:00:01 Isengard systemd[14494]: Reached target Default. Jan 01 01:00:01 Isengard systemd[14494]: Startup finished in 67ms. Jan 01 01:00:01 Isengard systemd[1]: Started User Manager for UID 0. Jan 01 01:00:01 Isengard CRON[14491]: pam_unix(crond:session): session closed for user root Jan 01 01:00:02 Isengard CRON[14493]: pam_unix(crond:session): session closed for user root Syslog clock has more precision: 3.6> 2017-01-01T00:55:01.837980+01:00 Isengard systemd 1 - - Removed slice User Slice of root. <3.6> 2017-01-01T00:59:59.007234+01:00 Isengard systemd 2287 - - Time has been changed <0.5> 2017-01-01T00:59:59.010999+01:00 Isengard kernel - - - [2151678.465702] Clock: inserting leap second 23:59:60 UTC <====== <3.6> 2017-01-01T00:59:59.014058+01:00 Isengard systemd 1 - - Time has been changed <10.6> 2017-01-01T01:00:01.763744+01:00 Isengard cron 14493 - - pam_unix(crond:session): session opened for user root by (uid=0) I understand this second propagates over nntp in some manner. Either explicitly, or as a consequence of the system clocks having adjusted for it. ntp log has this: 31 Dec 02:38:57 ntpd[1749]: kernel reports leap second insertion scheduled 1 Jan 01:03:31 ntpd[1749]: kernel reports leap second has occurred 1 Jan 01:03:31 ntpd[1749]: kernel reports leap second has occurred So ntpd is told by the kernel what is going to happen, 22 hours before. Now, the next step is learning what happens at a stratum one server. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)