Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 58294 - Un-parsable frequency in /etc/ntp/drift
Un-parsable frequency in /etc/ntp/drift
Product: Red Hat Linux
Classification: Retired
Component: ntp (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Harald Hoyer
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2002-01-13 07:14 EST by Samuli Kärkkäinen
Modified: 2007-04-18 12:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-01-17 10:35:09 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2002:230 normal SHIPPED_LIVE New ntp package fixes a bug in parsing command line options 2002-10-10 00:00:00 EDT

  None (edit)
Description Samuli Kärkkäinen 2002-01-13 07:14:25 EST
Description of Problem:
When ntpd is started, it syslogs a message "Un-parsable frequency in
/etc/ntp/drift" into /var/log/messages. Removing that file (and restarting ntpd
is needed) seems to fix the issue. I'm not sure if ntpd actually starts despite
that message.

How Reproducible: always
Comment 1 Harald Hoyer 2002-01-28 06:08:57 EST
ntpd should update this file on its own. You may
$ echo '0.0' >/etc/ntp/drift

If that does not help you may attach or paste the contents of the file here..
Comment 2 Harald Hoyer 2002-01-29 05:24:33 EST
fixed in 4.1.0b-5
Comment 3 John Flanagan 2003-02-14 16:02:08 EST
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.