Commit 44b96c5a authored by Eric S. Raymond's avatar Eric S. Raymond

In docs/fix various typos and minor markup errors.

parent 8f9e0752
......@@ -164,9 +164,8 @@ a residual frequency error less than 1 PPM. The measurement interval can
be changed using the `stepout` option of the
link:miscopt.html#tinker[`tinker`] command.
//FIXME:2 lines down 'mext'
In order to reduce the clock offset error at restart, the reference
implementation mext disables oscillator frequency discipline and enables
implementation next disables oscillator frequency discipline and enables
clock offset discipline with a small time constant. This is designed to
quickly reduce the clock offset error without causing a frequency surge.
This configuration is continued for an interval of five-min, after which
......
......@@ -78,8 +78,7 @@ current supplier.
=== Configuration ===
//FIXME: Backticks and quotes not rendering properly
The edge of the `PPS` signal that is `on-time' can be set with `flag2`.
The edge of the PPS signal that is on-time can be set with `flag2`.
There is currently no way to cause the `PPS` signal to control the
kernel `PLL`.
......
......@@ -112,7 +112,6 @@ written as-is to the `clockstats` file.
`time1` 'time'::
Specifies the time offset calibration factor, in seconds and fraction,
to be used for the West satellite, with default 0.0.
//FIXME: Not sure how to put '. ' before Specifies under stratum w/o creating a list
`time2 time`::
Specifies the time offset calibration factor, in seconds and fraction,
to be used for the East satellite, with default 0.0.
......
......@@ -406,10 +406,9 @@ time1 _time_ ::
The default value depends on the clock type.
time2 _time_ ::
If flag1 is 0, time2 specifies the offset of the PPS signal from the
actual time (PPS fine tuning).
//FIXME: Description should be on two lines
If flag1 is 1, time2 specifies the number of seconds a receiver with a
premium local oscillator can be trusted after losing synchronisation.
actual time (PPS fine tuning). If flag1 is 1, time2 specifies the
number of seconds a receiver with a premium local oscillator can be
trusted after losing synchronisation.
stratum _stratum_ ::
The stratum for this reference clock.
refid _refid_ ::
......
......@@ -30,8 +30,8 @@ Last update: 31-Mar-2014 05:41
Note: The NTP Version 4 software contained in this distribution is
available without charge under the conditions set forth in the
link:copyright.html[Copyright Notice].
//FIXME: Using a quote block here is dodgy, should be an admonition.
_____
[note]
It is very important that readers understand that the NTP document
collection began 25 years ago and remains today a work in progress. It
has evolved as new features were invented and old features retired. It
......@@ -43,16 +43,15 @@ the online collection at {project-weblink} is normally included in the most
recent snapshot, but might not agree with an earlier snapshot or
release version.
_____
This distribution is an implementation of RFC-5905 "Network Time Protocol Version 4: Protocol and Algorithms Specification". +
NTP is widely used to synchronize a computer to Internet time servers
or other sources, such as a radio or satellite receiver or telephone
modem service. It can also be used as a server for dependent clients. It
provides accuracies typically less than a millisecond on LANs and up to
a few milliseconds on WANs. Typical NTP configurations utilize multiple
redundant servers and diverse network paths in order to achieve high
accuracy and reliability.
This distribution is an implementation of RFC-5905 "Network Time
Protocol Version 4: Protocol and Algorithms Specification". NTP is
widely used to synchronize a computer to Internet time servers or
other sources, such as a radio or satellite receiver or telephone
modem service. It can also be used as a server for dependent
clients. It provides accuracies typically less than a millisecond on
LANs and up to a few milliseconds on WANs. Typical NTP configurations
utilize multiple redundant servers and diverse network paths in order
to achieve high accuracy and reliability.
This distribution includes a simulation framework in which substantially
all the runtime NTP operations and most features can be tested and
......
......@@ -143,47 +143,46 @@ entries than you expected. Support for some very ancient drivers
(notably, those rendered obsolete by the WWVB modulation change in
2013) has been dropped in order to reduce our maintainance load.
//FIXME: Either add symbols to all entries or remove all
* link:driver1.html[Type 1] Undisciplined Local Clock (`LOCAL`)
* link:driver1.html[Type 1] Undisciplined Local Clock
* Type 2 reserved
* Type 3 reserved
* link:driver4.html[Type 4] Generic Spectracom Receivers (`SPECTRACOM`)
* link:driver5.html[Type 5] TrueTime GPS/GOES/OMEGA Receivers (`TRUETIME`)
* link:driver6.html[Type 6] IRIG Audio Decoder (`IRIG_AUDIO`)
* link:driver7.html[Type 7] Radio CHU Audio Demodulator/Decoder (`CHU`)
* link:driver8.html[Type 8] Generic Reference Driver (`PARSE`)
* link:driver9.html[Type 9] Magnavox MX4200 GPS Receiver (`GPS_MX4200`)
* link:driver10.html[Type 10] Austron 2200A/2201A GPS Receivers (`GPS_AS2201`)
* link:driver11.html[Type 11] Arbiter 1088A/B GPS Receiver (`GPS_ARBITER`)
* link:driver4.html[Type 4] Generic Spectracom Receivers
* link:driver5.html[Type 5] TrueTime GPS/GOES/OMEGA Receivers
* link:driver6.html[Type 6] IRIG Audio Decoder
* link:driver7.html[Type 7] Radio CHU Audio Demodulator/Decoder
* link:driver8.html[Type 8] Generic Reference Driver
* link:driver9.html[Type 9] Magnavox MX4200 GPS Receiver
* link:driver10.html[Type 10] Austron 2200A/2201A GPS Receivers
* link:driver11.html[Type 11] Arbiter 1088A/B GPS Receiver
* Type 12 reserved
* Type 13 reserved
* Type 14 reserved
* Type 15 reserved
* link:driver16.html[Type 16] Bancomm GPS/IRIG Receiver (`GPS_BANCOMM`)
* link:driver16.html[Type 16] Bancomm GPS/IRIG Receiver
* Type 17 reserved
* link:driver18.html[Type 18] NIST/USNO/PTB Modem Time Services (`ACTS_MODEM`)
* link:driver18.html[Type 18] NIST/USNO/PTB Modem Time Services
* Type 19 reserved
* link:driver20.html[Type 20] Generic NMEA GPS Receiver (`NMEA`)
* link:driver20.html[Type 20] Generic NMEA GPS Receiver
* Type 21 reserved
* link:driver22.html[Type 22] PPS Clock Discipline (`PPS`)
* link:driver22.html[Type 22] PPS Clock Discipline
* Type 23 reserved
* Type 24 reserved
* Type 25 reserved
* link:driver26.html[Type 26] Hewlett Packard 58503A GPS Receiver (`GPS_HP`)
* link:driver27.html[Type 27] Arcron MSF Receiver (`MSF_ARCRON`)
* link:driver28.html[Type 28] Shared Memory Driver (`SHM`)
* link:driver29.html[Type 29] Trimble Navigation Palisade GPS (`GPS_PALISADE`)
* link:driver30.html[Type 30] Motorola UT Oncore GPS (`GPS_ONCORE`)
* link:driver31.html[Type 31] Rockwell Jupiter GPS (`GPS_JUPITER`)
* link:driver26.html[Type 26] Hewlett Packard 58503A GPS Receiver
* link:driver27.html[Type 27] Arcron MSF Receiver
* link:driver28.html[Type 28] Shared Memory Driver
* link:driver29.html[Type 29] Trimble Navigation Palisade GPS
* link:driver30.html[Type 30] Motorola UT Oncore GPS
* link:driver31.html[Type 31] Rockwell Jupiter GPS
* Type 32 reserved
* link:driver33.html[Type 33] Dumb Clock (`DUMBCLOCK`)
* link:driver33.html[Type 33] Dumb Clock
* Type 34 reserved
* link:driver35.html[Type 35] Conrad Parallel Port Radio Clock (`PCF`)
* link:driver35.html[Type 35] Conrad Parallel Port Radio Clock
* Type 36 reserved
* link:driver37.html[Type 37] Forum Graphic GPS Dating station (`FG`)
* link:driver38.html[Type 38] hopf GPS/DCF77 6021/komp for Serial Line (`HOPF_S`)
* link:driver39.html[Type 39] hopf GPS/DCF77 6039 for PCI-Bus (`HOPF_P`)
* link:driver40.html[Type 40] JJY Receivers (`JJY`)
* link:driver37.html[Type 37] Forum Graphic GPS Dating station
* link:driver38.html[Type 38] hopf GPS/DCF77 6021/komp for Serial Line
* link:driver39.html[Type 39] hopf GPS/DCF77 6039 for PCI-Bus
* link:driver40.html[Type 40] JJY Receivers
* Type 41 reserved
* link:driver42.html[Type 42] Zyfer GPStarplus Receiver
* Type 43 reserved
......
......@@ -7,7 +7,7 @@
== NAME ==
ntp.conf - Network Time Protocol (NTP) daemon configuration file format
== SYNOPSIS --
== SYNOPSIS ==
/etc/ntp.conf
== DESCRIPTION ==
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment