Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 2752 - /etc/ntp.conf apparently specifies incorrect stratum
Summary: /etc/ntp.conf apparently specifies incorrect stratum
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: xntp3
Version: 6.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jay Turner
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-05-12 01:41 UTC by dfm
Modified: 2015-01-07 23:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 1999-05-12 10:56:02 UTC


Attachments (Terms of Use)

Description dfm 1999-05-12 01:41:52 UTC
It appears that the ntp.conf file in the xntp3 package
shipped with RH 6.0 contains a stray character. In previous
versions of Red Hat, the file read, in part,

fudge   127.127.1.0 stratum 0

Now, however, it reads:

fudge   127.127.1.0 stratum 10

Nonetheless, the comment block above this line continues to
speak of using stratum 0. I suspect the new version of the
file to stem from a typo.

If I'm wrong, the comment should probably be updated to
reflect (and perhaps explain) the change.

Comment 1 Jeff Johnson 1999-05-12 10:56:59 UTC
The change was made so that machines without a reference clock
did not inadvertantly start honking NTP at stratum 0. The comment,
not the configuration, is incorrect.

In order to configure and use xntp3 correctly, see the URL
http://www.cis.udel.edu/~ntp. Basically you will need to find
a reference clock server that will be added to ntp.conf as
	server	your_reference_clock_server

Red Hat can't supply a default refernce clock server in ntp.conf
because of the number of installed Red Hat systems.


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