Bug 1381600 - ntpd -x steps clock on leap second
Summary: ntpd -x steps clock on leap second
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ntp
Version: 6.6
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: rc
: ---
Assignee: Miroslav Lichvar
QA Contact: Jakub Prokes
URL:
Whiteboard:
Depends On: 1190619
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-04 14:05 UTC by Marcel Kolaja
Modified: 2019-12-16 06:59 UTC (History)
17 users (show)

Fixed In Version: ntp-4.2.6p5-2.el6_5.2
Doc Type: Bug Fix
Doc Text:
Previously, when the ntpd daemon was configured with the "-x" option to adjust the system clock slowly instead of changing the time instantaneously, the system clock was incorrectly changed instantaneously when a leap second occurred. In certain applications, this could lead to a variety of system clock related problems, such as incorrect event sorting or triggering. To fix this bug, ntpd now adjusts for the leap second slowly over a long interval, which prevents the described problems.
Clone Of: 1190619
Environment:
Last Closed: 2016-10-19 15:20:03 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Network Time Protocol 2745 0 None None None 2019-04-24 13:28:15 UTC
Red Hat Knowledge Base (Solution) 1379783 0 None None None 2016-10-04 14:05:47 UTC
Red Hat Product Errata RHBA-2016:2081 0 normal SHIPPED_LIVE ntp bug fix update 2016-10-19 18:59:33 UTC

Description Marcel Kolaja 2016-10-04 14:05:35 UTC 
This bug has been copied from bug #1190619 and has been proposed
to be backported to 6.5 z-stream (EUS).
Comment 7 errata-xmlrpc 2016-10-19 15:20:03 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2081.html
Note You need to log in before you can comment on or make changes to this bug.