Bug 4238
Summary: | xntpd can't fix clocks way out of date | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | nelson |
Component: | xntp3 | Assignee: | David Lawrence <dkl> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1999-07-28 15:03:39 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
nelson
1999-07-28 14:52:53 UTC
Add the host that you wish to synchronize against using ntpdate to /etc/ntp/step-tickers. Look at /etc/rc.d/init.d/xntpd for details. We do not synchronize the hardware clock with the system clock because of the numerous support issues associated with setting the hardware clock on multiple platforms. For example, dual booting machines often require localtime rather than UTC, and many BIOS's do not support daylight saveings times. |