Bug 88149
Summary: | dateconfig fails to correctly update the system clock | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <potsmaster> | ||||
Component: | dateconfig | Assignee: | Brent Fox <bfox> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 7.3 | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2006-02-21 18:52:31 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: | |||||||
Attachments: |
|
Description
Need Real Name
2003-04-06 22:48:24 UTC
Can you attach your /etc/ntp.conf file? Created attachment 91754 [details]
ntp conf as requested
this file has been modified several times since filing the bug. dateconfig
still fails to update the system clock. i've been running ntpdate from cron,
which has been a bit more successful.
Hmm...the file looks ok to me. I really have no idea why this would happen. ntp works fine for all of us here. I'm not sure what to do. :( What is the contents of the /etc/ntp/step-tickers file? /etc/ntp/step-tickers is a zero-length file. what's really disturbing about this issue is my system clock is now losing as much as 5 minutes a day. this started happening after i upgraded my kernel to 2.4.18-27.7.x,,, Hmm...I'm becoming convinced that this problem has nothing to do with dateconfig. After doing a quick Bugzilla query, I ran across bug #66417. This sounds almost identical to your problem. I think this report is a duplicate of that bug. *** This bug has been marked as a duplicate of 66417 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |