| [chrony-dev] Handling of leap seconds |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: [chrony-dev] Handling of leap seconds
- From: Dennis Law <cmlaw1993@xxxxxxxxx>
- Date: Mon, 2 Mar 2020 09:41:48 +0800
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=jFekpgMZ8Y7qcdKBc9E8aZ4wBB0KE/ZacD/OPUdm9wM=; b=lXcJnEIUH3wSGy8sGL4PXrE4dmVYWT/DPlk0JmdBMXk4c7mOYE7Ecw/yPMmgupEEXd ChdNZ8nDVteX3cxQ0hjpaT1/bYstuKNMSEfNW4q3xZhAUqvIrouBbMV8w6XOUpzK59gU gQc63j0QAjqFZ6uMzmjJDivpiQ2kdjJTIZpXfDjoK4llYSXt004J9ouIqO/KkfSVyuh1 zwBEG2TylF4sO517sfUXXOZYI4nr04xb3OLKGvGu9HL616udZkMRtfMxlQjOGgH68Jsc EY4WnMipNadqqAJAXEPxQQdkxpaGpv6cZq8T3bsNAZ9CKGeoZpdUBj3lrfuOTXO4oQxp aRRQ==
Hi all,
It seems that when the program finds out about a leap second occurrence too
close to the occurrence itself (within 5 seconds), it simply does not
attempt to correct it.