Bug 1117882
Summary: | rebase chrony to 2.1.1 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Miroslav Lichvar <mlichvar> |
Component: | chrony | Assignee: | Miroslav Lichvar <mlichvar> |
Status: | CLOSED ERRATA | QA Contact: | Jakub Prokes <jprokes> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 7.0 | CC: | jprokes, jscotka, kdube, lmiksik, ovasik, pbokoc, snagar |
Target Milestone: | rc | Keywords: | Rebase |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | chrony-2.1.1-1.el7 | Doc Type: | Rebase: Bug Fixes and Enhancements |
Doc Text: |
The chrony packages have been upgraded to upstream version 2.1.1, which provides a number of bug fixes and enhancements over the previous version. Notable enhancements include:
* Updated to NTP version 4 (RFC 5905)
* Added pool directive to specify pool of NTP servers
* Added leapsecmode directive to select how to correct clock for leap second
* Added smoothtime directive to smooth served time and enable leap smear
* Added asynchronous name resolving with POSIX threads
* Ready for year 2036 (next NTP era)
* Improved clock control
* Networking code reworked to open separate client sockets for each NTP server
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-19 08:29:31 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1095800, 1191019 |
Description
Miroslav Lichvar
2014-07-09 15:14:39 UTC
chrony-2.0-pre1 was released 2 months ago, final 2.0 will likely be released in a few weeks. There are some nice improvements, e.g. update to NTPv4 (RFC 5905), support for NTP pools, or new leap second handling modes. http://git.tuxfamily.org/chrony/chrony.git/tree/NEWS 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/RHSA-2015-2241.html |