[system-administrators-guide] Typos, markup improvements, remove some white space
stephenw
stephenw at fedoraproject.org
Wed Jul 10 07:47:50 UTC 2013
commit 6331af258496b29cd57cd5a6ae780e92554ac7f8
Author: Stephen Wadeley <swadeley at redhat.com>
Date: Wed Jul 10 09:43:29 2013 +0200
Typos, markup improvements, remove some white space
en-US/Configuring_NTP_using_the_Chrony_suite.xml | 97 +++++++++++-----------
1 files changed, 47 insertions(+), 50 deletions(-)
---
diff --git a/en-US/Configuring_NTP_using_the_Chrony_suite.xml b/en-US/Configuring_NTP_using_the_Chrony_suite.xml
index 0b5f552..8602da4 100644
--- a/en-US/Configuring_NTP_using_the_Chrony_suite.xml
+++ b/en-US/Configuring_NTP_using_the_Chrony_suite.xml
@@ -24,8 +24,7 @@ There is a choice between the daemons <systemitem class="daemon">ntpd</systemite
<section id="sect-differences_between_ntpd_and_chronyd">
<title>Differences Between ntpd and chronyd</title>
<para>
- One of the main differences between <systemitem class="daemon">ntpd</systemitem> and <systemitem class="daemon">chronyd</systemitem> is in the
- algorithms used to control the computer's clock. Things <systemitem class="daemon">chronyd</systemitem> can do better than <systemitem class="daemon">ntpd</systemitem> are:
+ One of the main differences between <systemitem class="daemon">ntpd</systemitem> and <systemitem class="daemon">chronyd</systemitem> is in the algorithms used to control the computer's clock. Things <systemitem class="daemon">chronyd</systemitem> can do better than <systemitem class="daemon">ntpd</systemitem> are:
</para>
<itemizedlist>
<listitem>
@@ -40,7 +39,7 @@ There is a choice between the daemons <systemitem class="daemon">ntpd</systemite
</listitem>
<listitem>
<para>
- <systemitem class="daemon">chronyd</systemitem> can usually synchronise the clock faster and with better time accuracy.
+ <systemitem class="daemon">chronyd</systemitem> can usually synchronise the clock faster and with better time accuracy.
</para>
</listitem>
<listitem>
@@ -104,7 +103,7 @@ Things <systemitem class="daemon">ntpd</systemitem> can do that <systemitem clas
</listitem>
<listitem>
<para>
- The <systemitem class="protocol">NTP</systemitem> daemon (<systemitem class="daemon">ntpd</systemitem>) should be considered for systems which are normally kept permanently on. Systems which are required to use broadcast or multicast IP, or to perform authentication of packets with the Autokey protocol, should consider using <systemitem class="daemon">ntpd</systemitem>. <application>Chrony</application> only supports symmetric key authentication, such as the use of <systemitem class="protocol">MD5</systemitem>, <systemitem class="protocol">SHA1</systemitem>, and <systemitem class="protocol">SHA256</systemitem> hash functions, whereas <systemitem class="daemon">ntpd</systemitem> supports the Autokey authentication protocol which can make use of the PKI system. Autokey is described in <citetitle pubwork="webpage">RFC5906</citetitle>.
+ The <systemitem class="protocol">NTP</systemitem> daemon (<systemitem class="daemon">ntpd</systemitem>) should be considered for systems which are normally kept permanently on. Systems which are required to use broadcast or multicast IP, or to perform authentication of packets with the <systemitem class="protocol">Autokey</systemitem> protocol, should consider using <systemitem class="daemon">ntpd</systemitem>. <application>Chrony</application> only supports symmetric key authentication using a message authentication code (MAC) with MD5, SHA1 or stronger hash functions, whereas <systemitem class="daemon">ntpd</systemitem> also supports the <systemitem class="protocol">Autokey</systemitem> authentication protocol which can make use of the PKI system. <systemitem class="protocol">Autokey</systemitem> is described in <citetitle pubwork="webpage">RFC5906</citetitle>.
</para>
</listitem>
</itemizedlist>
@@ -164,7 +163,7 @@ Optionally specify a host, subnet, or network from which to allow <systemitem cl
<listitem>
<screen>allow 2001:db8::/32</screen>
<para>
- Use this form to specify an IPv6 address to be allowed access.
+ Use this form to specify an <systemitem class="protocol">IPv6</systemitem> address to be allowed access.
</para>
</listitem>
</orderedlist>
@@ -176,7 +175,7 @@ Optionally specify a host, subnet, or network from which to allow <systemitem cl
<term>cmdallow</term>
<listitem>
<para>
- This is similar to the <command>allow</command> directive (see section allow), except that it allows control access (rather than <systemitem class="protocol">NTP</systemitem> client access) to a particular subnet or host. (By <quote>control access</quote> is meant that <application>chronyc</application> can be run on those hosts and successfully connect to <systemitem class="daemon">chronyd</systemitem> on this computer.) The syntax is identical. There is also a <command>cmddeny</command> all directive with similar behaviour to the <command>cmdallow</command> all directive. </para>
+ This is similar to the <command>allow</command> directive (see section <command>allow</command>), except that it allows control access (rather than <systemitem class="protocol">NTP</systemitem> client access) to a particular subnet or host. (By <quote>control access</quote> is meant that <application>chronyc</application> can be run on those hosts and successfully connect to <systemitem class="daemon">chronyd</systemitem> on this computer.) The syntax is identical. There is also a <command>cmddeny</command> all directive with similar behavior to the <command>cmdallow</command> all directive.</para>
</listitem>
</varlistentry>
@@ -184,7 +183,7 @@ Optionally specify a host, subnet, or network from which to allow <systemitem cl
<term>dumpdir</term>
<listitem>
<para>
- Path to the directory to save the measurement history across restarts of <systemitem class="daemon">chronyd</systemitem> (assuming no changes are made to the system clock behaviour whilst it is not running). If this capability is to be used (via the <command>dumponexit</command> command in the configuration file, or the <command>dump</command> command in chronyc), the <command>dumpdir</command> command should be used to define the directory where the measurement histories are saved. </para>
+ Path to the directory to save the measurement history across restarts of <systemitem class="daemon">chronyd</systemitem> (assuming no changes are made to the system clock behavior whilst it is not running). If this capability is to be used (via the <command>dumponexit</command> command in the configuration file, or the <command>dump</command> command in <application>chronyc</application>), the <command>dumpdir</command> command should be used to define the directory where the measurement histories are saved.</para>
</listitem>
</varlistentry>
@@ -192,7 +191,7 @@ Optionally specify a host, subnet, or network from which to allow <systemitem cl
<term>dumponexit</term>
<listitem>
<para>
- If this command is present, it indicates that <systemitem class="daemon">chronyd</systemitem> should save the measurement history for each of its time sources recorded whenever the program exits. (See the <command>dumpdir</command> command above)</para>
+ If this command is present, it indicates that <systemitem class="daemon">chronyd</systemitem> should save the measurement history for each of its time sources recorded whenever the program exits. (See the <command>dumpdir</command> command above).</para>
</listitem>
</varlistentry>
@@ -204,7 +203,7 @@ Optionally specify a host, subnet, or network from which to allow <systemitem cl
<para>
An example of the command is:
<screen>local stratum 10</screen>
-A large value of 10 indicates that the clock is so many hops away from a reference clock that its time is fairly unreliable. Put another way, if the computer ever has access to another computer which is ultimately synchronized to a reference clock, it will almost certainly be at a stratum less than 10. Therefore, the choice of a high value like 10 for the <command>local</command> command prevents the machine’s own time from ever being confused with real time, were it ever to leak out to clients that have visibility of real servers. </para>
+A large value of 10 indicates that the clock is so many hops away from a reference clock that its time is fairly unreliable. Put another way, if the computer ever has access to another computer which is ultimately synchronized to a reference clock, it will almost certainly be at a stratum less than 10. Therefore, the choice of a high value like 10 for the <command>local</command> command prevents the machine’s own time from ever being confused with real time, were it ever to leak out to clients that have visibility of real servers.</para>
</listitem>
</varlistentry>
<varlistentry>
@@ -249,7 +248,7 @@ A large value of 10 indicates that the clock is so many hops away from a referen
<term>refclocks</term>
<listitem>
<para>
- This option logs the raw and filtered reference clock measurements to a file called <filename>refclocks.log</filename>.
+ This option logs the raw and filtered reference clock measurements to a file called <filename>refclocks.log</filename>.
</para>
</listitem>
</varlistentry>
@@ -257,7 +256,7 @@ A large value of 10 indicates that the clock is so many hops away from a referen
<term>tempcomp</term>
<listitem>
<para>
- This option logs the temperature measurements and system rate compensations to a file called <filename>tempcomp.log</filename>.
+ This option logs the temperature measurements and system rate compensations to a file called <filename>tempcomp.log</filename>.
</para>
</listitem>
</varlistentry>
@@ -265,7 +264,7 @@ A large value of 10 indicates that the clock is so many hops away from a referen
<term>refclocks</term>
<listitem>
<para>
- This option logs the raw and filtered reference clock measurements to a file called <filename>refclocks.log</filename>.
+ This option logs the raw and filtered reference clock measurements to a file called <filename>refclocks.log</filename>.
</para>
</listitem>
</varlistentry>
@@ -274,7 +273,7 @@ A large value of 10 indicates that the clock is so many hops away from a referen
<term>refclocks</term>
<listitem>
<para>
- This option logs the raw and filtered reference clock measurements to a file called <filename>refclocks.log</filename>.
+ This option logs the raw and filtered reference clock measurements to a file called <filename>refclocks.log</filename>.
</para>
</listitem>
</varlistentry>
@@ -314,7 +313,7 @@ An example of the use of this directive is:
<para>
An example of the use of this directive is:
<screen>makestep 1000 10</screen>
-This would step the system clock if the adjustment is larger than 1000 seconds, but only in the first ten clock updates.
+This would step the system clock if the adjustment is larger than 1000 seconds, but only in the first ten clock updates.
</para>
</listitem>
</varlistentry>
@@ -326,7 +325,7 @@ This would step the system clock if the adjustment is larger than 1000 seconds,
<para>
An example of the use of this directive is:
<screen>maxchange 1000 1 2</screen>
-After the first clock update, <systemitem class="daemon">chronyd</systemitem> will check the offset on every clock update, it will ignore two adjustments larger than 1000 seconds and exit on another one.
+After the first clock update, <systemitem class="daemon">chronyd</systemitem> will check the offset on every clock update, it will ignore two adjustments larger than 1000 seconds and exit on another one.
</para>
</listitem>
</varlistentry>
@@ -354,7 +353,7 @@ It should be noted that this is not the only means of protection against using u
<term>noclientlog</term>
<listitem>
<para>
-This directive, which takes no arguments, specifies that client accesses are not to be logged. Normally they are logged, allowing statistics to be reported using the clients command in <application>chronyc</application>.
+This directive, which takes no arguments, specifies that client accesses are not to be logged. Normally they are logged, allowing statistics to be reported using the clients command in <application>chronyc</application>.
</para>
</listitem>
</varlistentry>
@@ -362,7 +361,7 @@ This directive, which takes no arguments, specifies that client accesses are not
<term>reselectdist</term>
<listitem>
<para>
- When <systemitem class="daemon">chronyd</systemitem> selects synchronisation source from available sources, it will prefer the one with minimum synchronization distance. However, to avoid frequent reselecting when there are sources with similar distance, a fixed distance is added to the distance for sources that are currently not selected. This can be set with the <option>reselectdist</option> option. By default, the distance is 100 microseconds.</para>
+ When <systemitem class="daemon">chronyd</systemitem> selects synchronization source from available sources, it will prefer the one with minimum synchronization distance. However, to avoid frequent reselecting when there are sources with similar distance, a fixed distance is added to the distance for sources that are currently not selected. This can be set with the <option>reselectdist</option> option. By default, the distance is 100 microseconds.</para>
<para>
The format of the syntax is:
<screen>reselectdist <replaceable>dist-in-seconds</replaceable></screen>
@@ -374,11 +373,11 @@ The format of the syntax is:
<term>stratumweight</term>
<listitem>
<para>
- The <command>stratumweight</command> directive sets how much distance should be added per stratum to the synchronisation distance when <systemitem class="daemon">chronyd</systemitem> selects the synchronisation source from available sources.</para>
+ The <command>stratumweight</command> directive sets how much distance should be added per stratum to the synchronisation distance when <systemitem class="daemon">chronyd</systemitem> selects the synchronization source from available sources.</para>
<para>
The format of the syntax is:
<screen>stratumweight <replaceable>dist-in-seconds</replaceable></screen>
-By default, <replaceable>dist-in-seconds</replaceable> is 1 second. This usually means that sources with lower stratum will be preferred to sources with higher stratum even when their distance is significantly worse. Setting <command>stratumweight</command> to 0 makes <systemitem class="daemon">chronyd</systemitem> ignore stratum when selecting the source.
+By default, <replaceable>dist-in-seconds</replaceable> is 1 second. This usually means that sources with lower stratum will be preferred to sources with higher stratum even when their distance is significantly worse. Setting <command>stratumweight</command> to 0 makes <systemitem class="daemon">chronyd</systemitem> ignore stratum when selecting the source.
</para>
</listitem>
</varlistentry>
@@ -393,9 +392,7 @@ The format of the syntax is:
<screen>rtcfile /var/lib/chrony/rtc</screen>
-<systemitem class="daemon">chronyd</systemitem> saves information in this file when it exits and when the writertc command is issued in <application>chronyc</application>. The information saved is the RTC’s error at some epoch, that epoch (in seconds since January 1 1970), and the rate at which the RTC gains or loses time.
-
-Not all real-time clocks are supported as their code system-specific.
+<systemitem class="daemon">chronyd</systemitem> saves information in this file when it exits and when the <command>writertc</command> command is issued in <application>chronyc</application>. The information saved is the RTC’s error at some epoch, that epoch (in seconds since January 1 1970), and the rate at which the RTC gains or loses time. Not all real-time clocks are supported as their code is system-specific. Note that if this directive is used then real-time clock should not be manually adjusted as this would interfere with <application>chrony</application>'s need to measure the rate at which the real-time clock drifts if it was adjusted at random intervals.
</para>
</listitem>
</varlistentry>
@@ -513,7 +510,7 @@ chronyc> <command>password HEX:A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</command
<para>
To install <application>chrony</application>, run the following command as root:
<screen>~]# <command>yum install chrony -y</command></screen>
- The default installation directory is <filename>/usr/local/sbin/</filename>
+ The default installation directory is <filename>/usr/local/sbin/</filename>.
</para>
</section>
@@ -562,7 +559,7 @@ chronyd.service - NTP client/server
<title>Checking chrony Tracking</title>
<para>
- To check chrony tracking, issue the following command:
+ To check <application>chrony</application> tracking, issue the following command:
<screen>~]$ <command>chronyc tracking</command>
Reference ID : 1.2.3.4 (a.b.c)
Stratum : 3
@@ -585,7 +582,7 @@ Leap status : Normal
<term>Reference ID</term>
<listitem>
<para>
- This is the refid and name (or IP address) if available, of the server to which the computer is currently synchronised. If this is 127.127.1.1 it means the computer is not synchronised to any external source and that you have the ‘local’ mode operating (via the local command in chronyc (see section local), or the <command>local</command> directive in the ‘/etc/chrony.conf’ file (see section local)). </para>
+ This is the reference ID and name (or IP address) if available, of the server to which the computer is currently synchronized. If this is <systemitem class="ipaddress">>127.127.1.1</systemitem it means the computer is not synchronized to any external source and that you have the <quote>local</quote> mode operating (via the local command in <application>chronyc</application>, or the <command>local</command> directive in the <filename>/etc/chrony.conf</filename> file (see section <command>local</command>)).</para>
</listitem>
</varlistentry>
@@ -593,7 +590,7 @@ Leap status : Normal
<term>Stratum</term>
<listitem>
<para>
- The stratum indicates how many hops away from a computer with an attached reference clock we are. Such a computer is a stratum-1 computer, so the computer in the example is two hops away (i.e. a.b.c is a stratum-2 and is synchronised from a stratum-1).</para>
+ The stratum indicates how many hops away from a computer with an attached reference clock we are. Such a computer is a stratum-1 computer, so the computer in the example is two hops away (that is to say, a.b.c is a stratum-2 and is synchronized from a stratum-1).</para>
</listitem>
</varlistentry>
<varlistentry>
@@ -607,7 +604,7 @@ Leap status : Normal
<term>System time</term>
<listitem>
<para>
- In normal operation, <systemitem class="daemon">chronyd</systemitem> never steps the system clock, because any jump in the timescale can have adverse consequences for certain application programs. Instead, any error in the system clock is corrected by slightly speeding up or slowing down the system clock until the error has been removed, and then returning to the system clock’s normal speed. A consequence of this is that there will be a period when the system clock (as read by other programs using the gettimeofday() system call, or by the date command in the shell) will be different from chronyd's estimate of the current true time (which it reports to <systemitem class="protocol">NTP</systemitem> clients when it is operating in server mode). The value reported on this line is the difference due to this effect.</para>
+ In normal operation, <systemitem class="daemon">chronyd</systemitem> never steps the system clock, because any jump in the timescale can have adverse consequences for certain application programs. Instead, any error in the system clock is corrected by slightly speeding up or slowing down the system clock until the error has been removed, and then returning to the system clock’s normal speed. A consequence of this is that there will be a period when the system clock (as read by other programs using the <function>gettimeofday()</function> system call, or by the date command in the shell) will be different from <systemitem class="daemon">chronyd</systemitem>'s estimate of the current true time (which it reports to <systemitem class="protocol">NTP</systemitem> clients when it is operating in server mode). The value reported on this line is the difference due to this effect.</para>
</listitem>
</varlistentry>
<varlistentry>
@@ -628,16 +625,16 @@ Leap status : Normal
<term>Frequency</term>
<listitem>
<para>
- The ‘frequency’ is the rate by which the system’s clock would be would be wrong if <systemitem class="daemon">chronyd</systemitem> was not correcting it. It is expressed in ppm (parts per million). For example, a value of 1ppm would mean that when the system’s clock thinks it has advanced 1 second, it has actually advanced by 1.000001 seconds relative to true time. </para>
+ The <quote>frequency</quote> is the rate by which the system’s clock would be would be wrong if <systemitem class="daemon">chronyd</systemitem> was not correcting it. It is expressed in ppm (parts per million). For example, a value of 1ppm would mean that when the system’s clock thinks it has advanced 1 second, it has actually advanced by 1.000001 seconds relative to true time.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Residual freq</term>
<listitem>
<para>
- This shows the ‘residual frequency’ for the currently selected reference source. This reflects any difference between what the measurements from the reference source indicate the frequency should be and the frequency currently being used.
+ This shows the <quote>residual frequency</quote> for the currently selected reference source. This reflects any difference between what the measurements from the reference source indicate the frequency should be and the frequency currently being used.
- The reason this is not always zero is that a smoothing procedure is applied to the frequency. Each time a measurement from the reference source is obtained and a new residual frequency computed, the estimated accuracy of this residual is compared with the estimated accuracy (see ‘skew’ next) of the existing frequency value. A weighted average is computed for the new frequency, with weights depending on these accuracies. If the measurements from the reference source follow a consistent trend, the residual will be driven to zero over time.
+ The reason this is not always zero is that a smoothing procedure is applied to the frequency. Each time a measurement from the reference source is obtained and a new residual frequency computed, the estimated accuracy of this residual is compared with the estimated accuracy (see <option>skew</option> next) of the existing frequency value. A weighted average is computed for the new frequency, with weights depending on these accuracies. If the measurements from the reference source follow a consistent trend, the residual will be driven to zero over time.
</para>
</listitem>
</varlistentry>
@@ -645,14 +642,14 @@ Leap status : Normal
<term>Skew</term>
<listitem>
<para>
- This is the estimated error bound on the frequency. </para>
+ This is the estimated error bound on the frequency.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Root delay</term>
<listitem>
<para>
- This is the total of the network path delays to the stratum-1 computer from which the computer is ultimately synchronised.
+ This is the total of the network path delays to the stratum-1 computer from which the computer is ultimately synchronized.
In certain extreme situations, this value can be negative. (This can arise in a symmetric peer arrangement where the computers’ frequencies are not tracking each other and the network delay is very short relative to the turn-around time at each computer.)
</para>
@@ -662,14 +659,14 @@ Leap status : Normal
<term>Root dispersion</term>
<listitem>
<para>
-This is the total dispersion accumulated through all the computers back to the stratum-1 computer from which the computer is ultimately synchronised. Dispersion is due to system clock resolution, statistical measurement variations etc. </para>
+This is the total dispersion accumulated through all the computers back to the stratum-1 computer from which the computer is ultimately synchronized. Dispersion is due to system clock resolution, statistical measurement variations etc.</para>
</listitem>
</varlistentry>
<varlistentry>
<term> Leap status</term>
<listitem>
<para>
- This is the leap status, which can be Normal, Insert second, Delete second or Not synchronised.
+ This is the leap status, which can be Normal, Insert second, Delete second or Not synchronized.
</para>
</listitem>
</varlistentry>
@@ -681,7 +678,7 @@ This is the total dispersion accumulated through all the computers back to the s
<para>
The sources command displays information about the current time sources that <systemitem class="daemon">chronyd</systemitem> is accessing.
-The optional argument -v can be specified, meaning verbose. In this case, extra caption lines are shown as a reminder of the meanings of the columns.
+The optional argument -v can be specified, meaning verbose. In this case, extra caption lines are shown as a reminder of the meanings of the columns.
<screen>~]$ <command>chronyc sources</command>
210 Number of sources = 3
MS Name/IP address Stratum Poll Reach LastRx Last sample
@@ -697,7 +694,7 @@ The columns are as follows:
<term>M</term>
<listitem>
<para>
-This indicates the mode of the source. ^ means a server, = means a peer and # indicates a locally connected reference clock.
+This indicates the mode of the source. <literal>^</literal> means a server, <literal>=</literal> means a peer and <literal>#</literal> indicates a locally connected reference clock.
</para>
</listitem>
</varlistentry>
@@ -705,15 +702,15 @@ This indicates the mode of the source. ^ means a server, = means a peer and # in
<term>S</term>
<listitem>
<para>
-This column indicates the state of the sources. * indicates the source to which <systemitem class="daemon">chronyd</systemitem> is current synchronised. + indicates other acceptable sources. ? indicates sources to which connectivity has been lost. x indicates a clock which <systemitem class="daemon">chronyd</systemitem> thinks is is a falseticker (i.e. its time is inconsistent with a majority of other sources). ~ indicates a source whose time appears to have too much variability. The ~ condition is also shown at start-up, until at least 3 samples have been gathered from it.
- </para>
+This column indicates the state of the sources. <quote>*</quote> indicates the source to which <systemitem class="daemon">chronyd</systemitem> is currently synchronized. <quote>+</quote> indicates acceptable sources which are combined with the selected source. <quote>-</quote> indicates acceptable sources which are excluded by the combining algorithm. <quote>?</quote> indicates sources to which connectivity has been lost or whose packets do not pass all tests. <quote>x</quote> indicates a clock which <systemitem class="daemon">chronyd</systemitem> thinks is is a falseticker (that is to say, its time is inconsistent with a majority of other sources). <quote>~</quote> indicates a source whose time appears to have too much
+ variability. The <quote>?</quote> condition is also shown at start-up, until at least 3 samples have been gathered from it.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Name/IP address</term>
<listitem>
<para>
-This shows the name or the IP address of the source, or refid for reference clocks.
+This shows the name or the IP address of the source, or reference ID for reference clocks.
</para>
</listitem>
</varlistentry>
@@ -721,7 +718,7 @@ This shows the name or the IP address of the source, or refid for reference cloc
<term>Stratum</term>
<listitem>
<para>
-This shows the stratum of the source, as reported in its most recently received sample. Stratum 1 indicates a computer with a locally attached reference clock. A computer that is synchronised to a stratum 1 computer is at stratum 2. A computer that is synchronised to a stratum 2 computer is at stratum 3, and so on.
+This shows the stratum of the source, as reported in its most recently received sample. Stratum 1 indicates a computer with a locally attached reference clock. A computer that is synchronized to a stratum 1 computer is at stratum 2. A computer that is synchronized to a stratum 2 computer is at stratum 3, and so on.
</para>
</listitem>
</varlistentry>
@@ -747,7 +744,7 @@ This shows the stratum of the source, as reported in its most recently received
<term>LastRx</term>
<listitem>
<para>
- This column shows how long ago the last sample was received from the source. This is normally in seconds. The letters m, h, d or y indicate minutes, hours, days or years. A value of 10 years indicates there were no samples received from this source yet.
+ This column shows how long ago the last sample was received from the source. This is normally in seconds. The letters <literal>m</literal>, <literal>h</literal>, <literal>d</literal> or <literal>y</literal> indicate minutes, hours, days or years. A value of 10 years indicates there were no samples received from this source yet.
</para>
</listitem>
</varlistentry>
@@ -769,7 +766,7 @@ This shows the stratum of the source, as reported in its most recently received
<para>
The <command>sourcestats</command> command displays information about the drift rate and offset estimation process for each of the sources currently being examined by <systemitem class="daemon">chronyd</systemitem>.
-The optional argument <option>-v</option> can be specified, meaning verbose. In this case, extra caption lines are shown as a reminder of the meanings of the columns.
+The optional argument <option>-v</option> can be specified, meaning verbose. In this case, extra caption lines are shown as a reminder of the meanings of the columns.
<screen>~]$ <command>chronyc sourcestats</command>
@@ -786,7 +783,7 @@ The columns are as follows:
<term>Name/IP address</term>
<listitem>
<para>
-This is the name or IP address of the <systemitem class="protocol">NTP</systemitem> server (or peer) or refid of the refclock to which the rest of the line relates.
+This is the name or IP address of the <systemitem class="protocol">NTP</systemitem> server (or peer) or reference ID of the reference clock to which the rest of the line relates.
</para>
</listitem>
</varlistentry>
@@ -818,7 +815,7 @@ This is the number of runs of residuals having the same sign following the last
<term>Frequency</term>
<listitem>
<para>
- This is the estimated residual frequency for the server, in parts per million. In this case, the computer’s clock is estimated to be running 1 part in 10**9 slow relative to the server.
+ This is the estimated residual frequency for the server, in parts per million. In this case, the computer’s clock is estimated to be running 1 part in <inlineequation><mathphrase>10<superscript>9</superscript></mathphrase></inlineequation> slow relative to the server.
</para>
</listitem>
</varlistentry>
@@ -955,7 +952,7 @@ commandkey 24
local stratum 10
initstepslew 20 master
allow 192.0.2.123</screen>
-Where <systemitem class="ipaddress">192.0.2.123</systemitem> is the address of the master, and <systemitem class="systemname">master</systemitem> is the host name of the master. These clinet will resynchronize the master if it restarts.
+Where <systemitem class="ipaddress">192.0.2.123</systemitem> is the address of the master, and <systemitem class="systemname">master</systemitem> is the host name of the master. These client will resynchronize the master if it restarts.
</para>
<para>
@@ -969,8 +966,8 @@ Where <systemitem class="ipaddress">192.0.2.123</systemitem> is the address of t
<title>Using chronyc</title>
-<section id="sect-Using_chronyc_chronyc_to_control_cronyd">
- <title>Using chronyc to Control cronyd</title>
+<section id="sect-Using_chronyc_chronyc_to_control_chronyd">
+ <title>Using chronyc to Control chronyd</title>
<para>
To make changes using the command line utility <application>chronyc</application> in interactive mode, enter the following command as root:
<screen>~]# <command>chronyc</command></screen>
@@ -978,7 +975,7 @@ Where <systemitem class="ipaddress">192.0.2.123</systemitem> is the address of t
</para>
<para>
The <application>chronyc</application> command prompt will be displayed as follows:</para>
- <screen>/chronyc></screen>
+ <screen>chronyc></screen>
<para>
You can type <command>help</command> to list all of the commands.
</para>
@@ -1012,7 +1009,7 @@ From the remote systems, the system administrator can issue commands after first
</para>
<para>
- The password or hash associated with the command key for a remote system is best obtained by <systemitem class="protocol">SSH</systemitem>. That is to say, an <systemitem class="protocol">SSH</systemitem> connection should be established to the remote machine and the ID of the command key from <filename>/etc/chrony.conf</filename> and the command key in <filename>/etc/chrony.keys</filename> memorised or stored securly for the duration of the session.
+ The password or hash associated with the command key for a remote system is best obtained by <systemitem class="protocol">SSH</systemitem>. That is to say, an <systemitem class="protocol">SSH</systemitem> connection should be established to the remote machine and the ID of the command key from <filename>/etc/chrony.conf</filename> and the command key in <filename>/etc/chrony.keys</filename> memorized or stored securely for the duration of the session.
</para>
</section>
@@ -1061,7 +1058,7 @@ From the remote systems, the system administrator can issue commands after first
</listitem>
<listitem>
<para>
- <filename>/usr/share/doc/chrony*/chrony.txt</filename> — User guide for the <application>chrony</application> suite.
+ <filename>/usr/share/doc/chrony*/chrony.txt</filename> — User guide for the <application>chrony</application> suite.
</para>
</listitem>
</itemizedlist>
More information about the docs-commits
mailing list