Fellow time-nuts, While not fancy by any means, my laptop captured the leap-second being inserted by this message in the /var/log/syslog: Jan 1 00:59:59 greytop kernel: [78458.839942] Clock: inserting leap second 23:59:60 UTC Gently pointing out it had registered a leap second and inserted it. This from using NTP servers, nothing fancy. Happy New Year and a Happy Leap-second! Cheers, Magnus

On 1 January 2017 at 01:00, Magnus Danielson <magnus@rubidium.dyndns.org> wrote: > Fellow time-nuts, > > While not fancy by any means, my laptop captured the leap-second being > inserted by this message in the /var/log/syslog: > Jan 1 00:59:59 greytop kernel: [78458.839942] Clock: inserting leap > second 23:59:60 UTC > Noting reported on my Sun Ultra 27 running OpenSolaris. Dec 31 23:55:02 hawk sendmail[4016]: [ID 801593 mail.info] uBVNt2jv004015: to=<root@hawk.local>, ctladdr=<root@hawk.local> (0/0), delay=00:00:00, xdelay=00:00:00, mailer=local, pri=30730, relay=local, dsn=2.0.0, stat=Sent Jan 1 00:00:02 hawk sendmail[4055]: [ID 801593 mail.info] v01002rm004055: from=root, size=319, class=0, nrcpts=1, msgid=<201701010000.v01002rm004055@hawk.local>, relay=root@localhost This OS has not been updated for years drkirkby@hawk:~$ cat /etc/release OpenSolaris Development snv_134 X86 Copyright 2010 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms. Assembled 01 March 2010 Dave

Good evening David, On 01/01/2017 02:27 AM, Dr. David Kirkby (Kirkby Microwave Ltd) wrote: > On 1 January 2017 at 01:00, Magnus Danielson <magnus@rubidium.dyndns.org> > wrote: > >> Fellow time-nuts, >> >> While not fancy by any means, my laptop captured the leap-second being >> inserted by this message in the /var/log/syslog: >> Jan 1 00:59:59 greytop kernel: [78458.839942] Clock: inserting leap >> second 23:59:60 UTC >> > > Noting reported on my Sun Ultra 27 running OpenSolaris. > > Dec 31 23:55:02 hawk sendmail[4016]: [ID 801593 mail.info] uBVNt2jv004015: > to=<root@hawk.local>, ctladdr=<root@hawk.local> (0/0), delay=00:00:00, > xdelay=00:00:00, mailer=local, pri=30730, relay=local, dsn=2.0.0, stat=Sent > Jan 1 00:00:02 hawk sendmail[4055]: [ID 801593 mail.info] v01002rm004055: > from=root, size=319, class=0, nrcpts=1, > msgid=<201701010000.v01002rm004055@hawk.local>, relay=root@localhost What NTP is this? There is security patches to be made to older NTPs. I had to shut down xntpd on several solaris machines to make them safe, as there was no way of configure them to become safe. That was a couple of years ago. > > This OS has not been updated for years > > drkirkby@hawk:~$ cat /etc/release > OpenSolaris Development snv_134 X86 > Copyright 2010 Sun Microsystems, Inc. All Rights Reserved. > Use is subject to license terms. > Assembled 01 March 2010 Ehm. While off-topic, let me tell you that we had to shut down the last Solaris machine we had on the computer club because we concluded that there where tools designed to target that generation of Solaris machines and take them over. It should not see public internet if powered on. The network is increasingly hostile, so patch your machines, and don't let any machines sit on public network unless you can patch them regularly and also do that. Cheers, Magnus

Here is my observation for NTP 'chronyd'. The NTP setup is based on 1PPS (from Trimble TB) and kernel extension (pps_core) As leap second event happens, I noticed the "system clock" (NTP machine) was one second behind. Then it took around 16 minutes for 'chronyd' to gradually align system clock to match the time. Now everything ticking in tact. Here is par of 'chronyd' log. I noticed four column changed from "+" to "N" 2016-12-31 23:41:24 72.38.129.202 + 2 111 111 1111 10 10 1.00 -2.252e-03 1.788e-02 1.063e-06 2.440e-02 2.791e-02 2016-12-31 23:46:37 206.108.0.132 + 2 111 111 1111 10 9 0.08 3.681e-03 1.391e-02 1.126e-06 7.019e-04 5.044e-01 2016-12-31 23:49:17 192.95.25.79 + 3 111 111 1111 10 60 0.83 -4.016e-03 1.607e-02 1.607e-06 1.222e-02 3.143e-02 2016-12-31 23:55:43 132.163.4.102 + 1 111 111 1111 10 10 0.99 2.366e-03 4.196e-02 1.073e-06 0.000e+00 0.000e+00 ======================================================================================================================== Date (UTC) Time IP Address L St 123 567 ABCD LP RP Score Offset Peer del. Peer disp. Root del. Root disp. ======================================================================================================================== 2016-12-31 23:58:43 72.38.129.202 + 2 111 111 1111 10 10 1.00 -3.424e-03 1.650e-02 1.062e-06 2.440e-02 4.349e-02 2017-01-01 00:03:57 206.108.0.132 N 2 111 111 1111 10 10 0.33 2.033e-03 1.051e-02 1.124e-06 7.019e-04 5.200e-01 2017-01-01 00:06:38 192.95.25.79 N 3 111 111 1111 10 60 0.78 -3.597e-03 1.616e-02 2.116e-06 1.222e-02 2.022e-02 2017-01-01 00:13:08 132.163.4.102 N 1 111 111 1111 10 10 1.00 2.218e-03 4.040e-02 1.059e-06 0.000e+00 0.000e+00 2017-01-01 00:15:58 72.38.129.202 N 2 111 111 1111 10 10 1.00 -1.609e-03 2.219e-02 1.063e-06 2.483e-02 3.131e-02 For the LH 5.0 - it took the snapshot. http://www.patoka.ca/OCXO/leap_sec.gif Alsom I noticed that LH 5.0 watch is little bit behind of the 'xclok' watch translated from NTP (and from this link https://uhr.ptb.de/). Regards, Vlad On 2016-12-31 20:55, Magnus Danielson wrote: > Good evening David, > > On 01/01/2017 02:27 AM, Dr. David Kirkby (Kirkby Microwave Ltd) wrote: >> On 1 January 2017 at 01:00, Magnus Danielson >> <magnus@rubidium.dyndns.org> >> wrote: >> >>> Fellow time-nuts, >>> >>> While not fancy by any means, my laptop captured the leap-second >>> being >>> inserted by this message in the /var/log/syslog: >>> Jan 1 00:59:59 greytop kernel: [78458.839942] Clock: inserting leap >>> second 23:59:60 UTC >>> >> >> Noting reported on my Sun Ultra 27 running OpenSolaris. >> >> Dec 31 23:55:02 hawk sendmail[4016]: [ID 801593 mail.info] >> uBVNt2jv004015: >> to=<root@hawk.local>, ctladdr=<root@hawk.local> (0/0), delay=00:00:00, >> xdelay=00:00:00, mailer=local, pri=30730, relay=local, dsn=2.0.0, >> stat=Sent >> Jan 1 00:00:02 hawk sendmail[4055]: [ID 801593 mail.info] >> v01002rm004055: >> from=root, size=319, class=0, nrcpts=1, >> msgid=<201701010000.v01002rm004055@hawk.local>, relay=root@localhost > > What NTP is this? > > There is security patches to be made to older NTPs. > I had to shut down xntpd on several solaris machines to make them > safe, as there was no way of configure them to become safe. That was a > couple of years ago. > >> >> This OS has not been updated for years >> >> drkirkby@hawk:~$ cat /etc/release >> OpenSolaris Development snv_134 X86 >> Copyright 2010 Sun Microsystems, Inc. All Rights Reserved. >> Use is subject to license terms. >> Assembled 01 March 2010 > > Ehm. While off-topic, let me tell you that we had to shut down the > last Solaris machine we had on the computer club because we concluded > that there where tools designed to target that generation of Solaris > machines and take them over. It should not see public internet if > powered on. > > The network is increasingly hostile, so patch your machines, and don't > let any machines sit on public network unless you can patch them > regularly and also do that. > > Cheers, > Magnus > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. -- WBW, V.P.

On Sun, Jan 1, 2017 at 9:00 AM, Magnus Danielson <magnus@rubidium.dyndns.org > wrote: > While not fancy by any means, my laptop captured the leap-second being > inserted by this message in the /var/log/syslog: > Jan 1 00:59:59 greytop kernel: [78458.839942] Clock: inserting leap > second 23:59:60 UTC > On my Ubuntu desktop, 17.04 -dev, this is the systemd journal: Jan 01 07:59:59 X201wily kernel: Clock: inserting leap second 23:59:60 UTC Jan 01 07:59:59 X201wily systemd[1484]: Time has been changed Jan 01 07:59:59 X201wily systemd[1]: Time has been changed No NTP was running. -- Sanjeev Gupta +65 98551208 http://www.linkedin.com/in/ghane

I added this message to the Linux kernel near the end of 1993. There is a companion message that indicates the removal of the leap second -- but this has never been seen (except in testing!). In retrospect, it isn't clear that jumping the clock by a second was the right decision, but, at the time, it was the "obvious" thing to do. Philip On 31/12/2016 20:00, Magnus Danielson wrote: > Fellow time-nuts, > > While not fancy by any means, my laptop captured the leap-second being > inserted by this message in the /var/log/syslog: > Jan 1 00:59:59 greytop kernel: [78458.839942] Clock: inserting leap > second 23:59:60 UTC >