mlich...@redhat.com said: >> * If Chrony reads leap-seconds.list should it also look at the >> leap second expiration and reject old files? > As currently chrony works, there would be no functional difference between > rejecting old file and using old file unless someone was interested in > replaying old leap seconds.
If you know that the data in the file covers "now", you can ignore the leap-pending in NTP packets from servers. If you know that the file has expired, you can keep track of leap-pending from servers and if you get more than x% or more than N (that agree) you can believe that a leap will happen soon and pass that to the kernel. -- These are my opinions. I hate spam. -- To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
