doc: fix typos in man pages
This commit is contained in:
parent
7d7bf915ac
commit
1834ee05e5
2 changed files with 8 additions and 8 deletions
|
@ -191,7 +191,7 @@ This option sets the NTP version number used in packets sent to the server.
|
||||||
This can be useful when the server runs an old NTP implementation that doesn't
|
This can be useful when the server runs an old NTP implementation that doesn't
|
||||||
respond to newer versions. The default version number is 4.
|
respond to newer versions. The default version number is 4.
|
||||||
|
|
||||||
[[pool]]*pool* _hostname_ [_option_]...::
|
[[pool]]*pool* _name_ [_option_]...::
|
||||||
The syntax of this directive is similar to that for the <<server,*server*>>
|
The syntax of this directive is similar to that for the <<server,*server*>>
|
||||||
directive, except that it is used to specify a pool of NTP servers rather than
|
directive, except that it is used to specify a pool of NTP servers rather than
|
||||||
a single NTP server. The pool name is expected to resolve to multiple addresses
|
a single NTP server. The pool name is expected to resolve to multiple addresses
|
||||||
|
@ -1465,7 +1465,7 @@ from the example line above):
|
||||||
. The estimated local clock error (_theta_ in RFC 5905). Positive indicates
|
. The estimated local clock error (_theta_ in RFC 5905). Positive indicates
|
||||||
that the local clock is slow of the remote source. [-4.966e-03]
|
that the local clock is slow of the remote source. [-4.966e-03]
|
||||||
. The peer delay (_delta_ in RFC 5905). [2.296e-01]
|
. The peer delay (_delta_ in RFC 5905). [2.296e-01]
|
||||||
. The peer dispersion (`epsilon' in RFC 5905). [1.577e-05]
|
. The peer dispersion (_epsilon_ in RFC 5905). [1.577e-05]
|
||||||
. The root delay (_DELTA_ in RFC 5905). [1.615e-01]
|
. The root delay (_DELTA_ in RFC 5905). [1.615e-01]
|
||||||
. The root dispersion (_EPSILON_ in RFC 5905). [7.446e-03]
|
. The root dispersion (_EPSILON_ in RFC 5905). [7.446e-03]
|
||||||
+
|
+
|
||||||
|
|
|
@ -78,7 +78,7 @@ This option disables resolving of IP addresses to hostnames (e.g. to avoid slow
|
||||||
DNS lookups).
|
DNS lookups).
|
||||||
|
|
||||||
*-c*::
|
*-c*::
|
||||||
This option enables printing of reports in a column-separated values (CSV)
|
This option enables printing of reports in a comma-separated values (CSV)
|
||||||
format. IP addresses will not be resolved to hostnames, time will be printed as
|
format. IP addresses will not be resolved to hostnames, time will be printed as
|
||||||
number of seconds since the epoch and values in seconds will not be converted
|
number of seconds since the epoch and values in seconds will not be converted
|
||||||
to other units.
|
to other units.
|
||||||
|
@ -177,11 +177,11 @@ This is the estimated local offset on the last clock update.
|
||||||
*RMS offset*:::
|
*RMS offset*:::
|
||||||
This is a long-term average of the offset value.
|
This is a long-term average of the offset value.
|
||||||
*Frequency*:::
|
*Frequency*:::
|
||||||
The '`frequency`' is the rate by which the system's clock would be would be
|
The '`frequency`' is the rate by which the system's clock would be wrong if
|
||||||
wrong if *chronyd* was not correcting it. It is expressed in ppm (parts per
|
*chronyd* was not correcting it. It is expressed in ppm (parts per million).
|
||||||
million). For example, a value of 1 ppm would mean that when the system's
|
For example, a value of 1 ppm would mean that when the system's clock thinks it
|
||||||
clock thinks it has advanced 1 second, it has actually advanced by 1.000001
|
has advanced 1 second, it has actually advanced by 1.000001 seconds relative to
|
||||||
seconds relative to true time.
|
true time.
|
||||||
+
|
+
|
||||||
As you can see in the example, the clock in the computer is not a very
|
As you can see in the example, the clock in the computer is not a very
|
||||||
good one - it would gain about 30 seconds per day if it wasn't corrected!
|
good one - it would gain about 30 seconds per day if it wasn't corrected!
|
||||||
|
|
Loading…
Reference in a new issue