Bug 1482565
Summary: | chrony rebase to 3.2 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Miroslav Lichvar <mlichvar> |
Component: | chrony | Assignee: | Miroslav Lichvar <mlichvar> |
Status: | CLOSED ERRATA | QA Contact: | Andrej Dzilský <adzilsky> |
Severity: | medium | Docs Contact: | Lenka Špačková <lkuprova> |
Priority: | high | ||
Version: | 7.4 | CC: | adzilsky, bwelterl, kenneth, mlichvar, psklenar, salmy, thozza |
Target Milestone: | rc | Keywords: | Rebase |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | chrony-3.2-1.el7 | Doc Type: | Release Note |
Doc Text: |
_chrony_ rebased to version 3.2
The _chrony_ packages have been upgraded to upstream version 3.2, which provides a number of bug fixes and enhancements over the previous version. Notable enhancements include:
* Support for hardware timestamping with bonding, bridging, and other logical interfaces that aggregate ethernet interfaces
* Support for transmit-only hardware timestamping with network cards that can timestamp only received Precision Time Protocol (PTP) packets but not Network Time Protocol (NTP) packets
* Improved stability of synchronization with hardware timestamping and interleaved modes
* An improved "leapsectz" option to automatically set the offset of the system clock between International Atomic Time (TAI) and Coordinated Universal Time (UTC)
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-04-10 12:06:26 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: | 1465928 |
Description
Miroslav Lichvar
2017-08-17 15:07:25 UTC
Seems we have no reggressions. Verified. 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://access.redhat.com/errata/RHBA-2018:0753 |