On Wed, Jan 4, 2017 at 2:52 PM, Achim Gratz <strom...@nexgo.de> wrote: > > I've kept to rasPi running through the leap second. >
Here's the (very much less exciting than Achim's analysis) dump of the relevant lines from /var/log/syslog on my Ubuntu 16.04 box that was running NTPsec during the leap second. Dec 31 18:59:59 harbormaster kernel: [14461.150782] Clock: inserting leap second 23:59:60 UTC Dec 31 18:59:59 harbormaster systemd[1]: Time has been changed Dec 31 18:59:59 harbormaster systemd[2163]: Time has been changed Dec 31 18:59:59 harbormaster systemd[1]: snapd.refresh.timer: Adding 1h 27min 14.876839s random time. Dec 31 18:59:59 harbormaster systemd[1]: apt-daily.timer: Adding 10h 37min 25.745ms random time. Dec 31 18:59:59 harbormaster systemd[1459]: Time has been changed Dec 31 18:59:59 harbormaster ntpd[6653]: SHM: stale/bad receive time, delay=-1s Dec 31 19:00:47 harbormaster ntpd[6653]: kernel reports leap second has occurred Dec 31 19:00:47 harbormaster ntpd[6653]: kernel reports leap second has occurred _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
