At the end of 2016, my openSUSE system reported: Clock: inserting leap second 23:59:60 UTC This always worries me, as there are a number of links in the chain. And it seems any can insert a leap second. I have two configurations on openSUSE systems: Use ntpd to sync time with a time server. My local ntp can be told whether to insert leap seconds. I have to assume that the ntp protocol ensures that the time communicated between systems is properly identified as to whether it has a leap second adjustment or not. gpsd and chrony. gpsd, it seems, can have a compiled-in leap second offset. If I understand this correctly, this offset will be added to the time gpsd makes available to clients. Can the clients know this offset has been added? chrony can also add a leap second, depending on how it is configured. In all cases, I am using openSUSE-compiled binaries. Is there a coordinated discussion of how these apps are compiled and configured (e.g., ntpd via yast)? Especially as relates to leap seconds. Redhat have some info at https://developers.redhat.com/blog/2015/06/01/five-different-ways-handle-lea.... But that still does not address how the deliverables are actually configured when compiled and then configured for use. The reason I am so interested is that we have been working to use the system clock (set with gpsd/chrony) to timestamp data via gettimeofday(). That time can be used to locate things in the GPS location data. The GPS time does not have leap seconds. So we are trying to be sure we have not missed anything. The data is collected in a moving vehicle. At 90 km/h, each second of error is 25 meters. So it is a rather important thing to track... Knowing how this is dealt with through the complete openSUSE chain is important. All pointers to information are welcome. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org