commit 79a93a2fb0c40508a091248583419b94893113dd
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Thu Jun 27 20:26:28 2013 +0200
Improving the section headings: Title Case
en-US/Configuring_NTP_using_the_Chrony_suite.xml | 78 +++++++++++-----------
1 files changed, 39 insertions(+), 39 deletions(-)
---
diff --git a/en-US/Configuring_NTP_using_the_Chrony_suite.xml
b/en-US/Configuring_NTP_using_the_Chrony_suite.xml
index 58a1674..4104a03 100644
--- a/en-US/Configuring_NTP_using_the_Chrony_suite.xml
+++ b/en-US/Configuring_NTP_using_the_Chrony_suite.xml
@@ -6,7 +6,7 @@
<!--Topics, Concepts:-->
<chapter
id="chap-Networking_Guide-Configuring_NTP_using_the_chrony_suite">
- <title>Configuring NTP using the chrony suite</title>
+ <title>Configuring NTP Using The chrony Suite</title>
<para>
Accurate time keeping is important for a number of reasons in IT. In networking for
example, accurate time stamps in packets and logs are required. In Linux systems, the
<systemitem class="protocol">NTP</systemitem> protocol is
implemented by a daemon running in user space.</para>
<para>
@@ -15,15 +15,15 @@
<para>
There is a choice between the daemons <systemitem
class="daemon">ntpd</systemitem> and <systemitem
class="daemon">chronyd</systemitem>, which are available from the repos
in the <package>ntp</package> and <package>chrony</package>
packages respectively. This section describes the use of the
<application>chrony</application> suite of utilities to update the daemon on
systems that do not fit into the conventional permanently networked, always on, dedicated
server category.
</para>
-<section id="sect-Networking_Guide-Introduction_to_the_chrony_suite">
- <title>Introduction to the chrony suite</title>
+<section id="sect-Introduction_to_the_chrony_suite">
+ <title>Introduction To The Chrony Suite</title>
<para>
<application>Chrony</application> consists of <systemitem
class="daemon">chronyd</systemitem>, a daemon that runs in user space,
and <application>chronyc</application>, a command line program for making
adjustments to <systemitem class="daemon">chronyd</systemitem>.
Systems which are not permanently connected, or not permanently powered up, take a
relatively long time to adjust their system clocks using the <systemitem
class="protocol">NTP</systemitem> time protocol. This is because many
small corrections are made based on observations of the clocks drift and offset.
Temperature changes, which may be significant when powering up a system, affect the
stability of hardware clocks. Although adjustments begin within a few milliseconds of
booting a system, acceptable accuracy may take anything from ten seconds from a warm
restart to a number of hours depending on your requirements, operating environment and
hardware. <application>Chrony</application> is a different implementat
ion of the <systemitem class="protocol">NTP</systemitem> protocol
than <systemitem class="daemon">ntpd</systemitem>, it can adjust the
system clock more rapidly.
</para>
</section>
<section id="sect-differences_between_ntpd_and_chronyd">
- <title>Differences between ntpd and chronyd</title>
+ <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:
@@ -96,8 +96,8 @@ Things <systemitem
class="daemon">ntpd</systemitem> can do that <systemitem clas
</itemizedlist>
</section>
-<section id="sect-Networking_Guide-Choosing_between_NTP_daemon">
- <title>Choosing between NTP daemons</title>
+<section id="sect-Choosing_between_NTP_daemon">
+ <title>Choosing Between NTP Daemons</title>
<itemizedlist>
<listitem>
<para>
@@ -111,21 +111,21 @@ Things <systemitem
class="daemon">ntpd</systemitem> can do that <systemitem clas
</listitem>
</itemizedlist>
</section>
-<section id="sect-Networking_Guide-Understanding_chronyd">
+<section id="sect-Understanding_chronyd">
<title>Understanding chronyd</title>
<para>
The <application>Chrony</application> daemon, <systemitem
class="daemon">chronyd</systemitem>, running in user space, makes
adjustments to the system clock which is running in the kernel. It does this by consulting
external time sources, using the <systemitem
class="protocol">NTP</systemitem> protocol, when ever network access
allows it to do so. When external references are not available, <systemitem
class="daemon">chronyd</systemitem> will use the last calculated drift
stored in the drift file. It can also be commanded manually to make corrections, by
<application>chronyc</application>.
</para>
</section>
-<section id="sect-Networking_Guide-Understanding_chronyc">
+<section id="sect-Understanding_chronyc">
<title>Understanding chronyc</title>
<para>
The <application>chrony</application> daemon, <systemitem
class="daemon">chronyd</systemitem>, can be controlled by the command
line utility <application>chronyc</application>. This utility provides a
command prompt which allows entering of a number of commands to make changes to
<systemitem class="daemon">chronyd</systemitem>. The default
configuration is for <systemitem class="daemon">chronyd</systemitem>
to only accept commands from a local instance of
<application>chronyc</application>, but
<application>chronyc</application> can be used to alter the configuration so
that <systemitem class="daemon">chronyd</systemitem> will allow
external control. That is to say, <application>chronyc</application> can be
run remotely after first configuring <systemitem
class="daemon">chronyd</systemitem> to accept remote connections. The
IP addresses allowed to connect to <systemitem
class="daemon">chronyd</systemitem> should be tightly
controlled.</para>
</section>
- <section
id="sect-Networking_Guide-Understanding_the_chrony_configuration_commands">
- <title>Understanding the chrony configuration commands</title>
+ <section id="sect-Understanding_the_chrony_configuration_commands">
+ <title>Understanding The chrony Configuration Commands</title>
<para>
<systemitem class="daemon">chronyd</systemitem>'s default
config file is <filename>/etc/chrony.conf</filename>. The
<option>-f</option> option can be used to specify an alternate config file
path. Refer to the <systemitem class="daemon">chronyd</systemitem>
man page for further options. We present here a selection of configuration options. For a
complete list of the directives that can be used see <citetitle
pubwork="webpage">http://chrony.tuxfamily.org/manual.html#Co...
<variablelist>
@@ -403,8 +403,8 @@ Not all real-time clocks are supported as their code system-specific.
</para>
</section>
-<section id="sect-Networking_Guide-Security_with_chronyc">
- <title>Security with chronyc</title>
+<section id="sect-Security_with_chronyc">
+ <title>Security With chronyc</title>
<para>
As access to <application>chronyc</application> allows changing
<systemitem class="daemon">chronyd</systemitem> just as editing the
configuration files would, access to <application>chronyc</application> should
be limited. Passwords or their hashes can be specified in the key file, to restrict the
use of <application>chronyc</application>. One of the entries is used to
restrict the use of operational commands and is referred to as the command key. In the
default configuration, a random command key is generated automatically on start. It should
not be necessary to specify or alter it manually.</para>
<para>Other entries in the key file can be used as <systemitem
class="protocol">NTP</systemitem> keys to authenticate packets received
from remote <systemitem class="protocol">NTP</systemitem> servers or
peers. The two sides need to share a key with identical ID, hash type and password in
their key file. This requires manually creating the keys and copying them over a secure
medium, such as <systemitem class="protocol">SSH</systemitem>. If
the key ID was, for example, 10 then the systems that act as clients must have a line in
their configuration files in the following format:
@@ -487,8 +487,8 @@ chronyc> <command>password
HEX:A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</command
<!--Topics, Tasks:-->
-<section id="sect-Networking_Guide-Checking_if_chrony_is_installed">
- <title>Checking if chrony is installed</title>
+<section id="sect-Checking_if_chrony_is_installed">
+ <title>Checking If chrony Is Installed</title>
<para>
To check if <application>chrony</application> is installed, run the
following command as root:
<screen>~]# yum install chrony</screen>
@@ -496,7 +496,7 @@ chronyc> <command>password
HEX:A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</command
</para>
</section>
- <section id="sect-Networking_Guide-Installing_chrony">
+ <section id="sect-Installing_chrony">
<title>Installing chrony</title>
<para>
To install <application>chrony</application>, run the following command as
root:
@@ -507,7 +507,7 @@ To install <application>chrony</application>, run the
following command as root:
<section id="sect-Checking_the_Status_of_chronyd">
- <title>Checking the Status of chronyd</title>
+ <title>Checking The Status Of chronyd</title>
<para>
To check the status of <systemitem
class="daemon">chronyd</systemitem>, issue the following command:
<screen>~]$ <command>systemctl status chronyd</command>
@@ -516,7 +516,7 @@ chronyd.service - NTP client/server
Active: active (running) since Wed 2013-06-12 22:23:16 CEST; 11h ago</screen>
</para>
</section>
- <section id="sect-Networking_Guide-Starting_chronyd">
+ <section id="sect-Starting_chronyd">
<title>Starting chronyd</title>
<para>
To start <systemitem
class="daemon">chronyd</systemitem>, issue the following command as
root:
@@ -529,7 +529,7 @@ chronyd.service - NTP client/server
<para>
</para>
</section>
- <section id="sect-Networking_Guide-Stopping_chronyd">
+ <section id="sect-Stopping_chronyd">
<title>Stopping chronyd</title>
<para>
To stop <systemitem
class="daemon">chronyd</systemitem>, issue the following command as
root:
@@ -542,14 +542,14 @@ chronyd.service - NTP client/server
</section>
- <section
id="sect-Networking_Guide-Checking_if_chrony_is_synchronized">
- <title>Checking if chrony is Synchronized</title>
+ <section id="sect-Checking_if_chrony_is_synchronized">
+ <title>Checking If chrony Is Synchronized</title>
<para>
To check if <application>chrony</application> is synchronized, make use
of the <command>tracking</command>, <command>sources</command>,
and <command>sourcestats</command> commands.
</para>
- <section id="sect-Networking_Guide-Checking_chrony_tracking">
- <title>Checking chrony tracking</title>
+ <section id="sect-Checking_chrony_tracking">
+ <title>Checking chrony Tracking</title>
<para>
To check chrony tracking, issue the following command:
@@ -666,8 +666,8 @@ This is the total dispersion accumulated through all the computers
back to the s
</variablelist>
</section>
- <section id="sect-Networking_Guide-Checking_chrony_sources">
- <title>Checking chrony sources</title>
+ <section id="sect-Checking_chrony_sources">
+ <title>Checking chrony Sources</title>
<para>
The sources command displays information about the current time sources that
<systemitem class="daemon">chronyd</systemitem> is accessing.
@@ -754,8 +754,8 @@ This shows the stratum of the source, as reported in its most recently
received
</para>
</section>
-<section id="sect-Networking_Guide-Checking_chrony_sourcestats">
- <title>Checking chrony sourcestats</title>
+<section id="sect-Checking_chrony_Source_Statistics">
+ <title>Checking chrony Source Statistics</title>
<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>.
@@ -841,8 +841,8 @@ This is the estimated error bounds on Freq (again in parts per
million).
</section>
</section>
-<section id="sect-Networking_Guide-Adjusting-the-System_Clock">
- <title>Manualy Adjusting the System Clock</title>
+<section id="sect-Adjusting-the-System_Clock">
+ <title>Manualy Adjusting The System Clock</title>
<para>
To update, or step, the system clock immediately, bypassing any adjustments in
progress by slewing the clock, issue the following commands as root:
<screen>~]# <command>chronyc</command>
@@ -857,8 +857,8 @@ This is the estimated error bounds on Freq (again in parts per
million).
</para>
</section>
-<section
id="sect-Networking_Guide-Setting_up_chrony_for_a_system_which_is_infrequently_connected">
- <title>Setting up chrony for a system which is infrequently
connected</title>
+<section
id="sect-Setting_up_chrony_for_a_system_which_is_infrequently_connected">
+ <title>Setting Up Chrony For A System Which Is Infrequently
Connected</title>
<para>
This example is intended for systems which use dial-on-demand connections. The normal
configuration should be sufficient for mobile and virtual devices which connect
intermittently. First, review and confirm that the default settings in the
<filename>/etc/chrony.conf</filename> are similar to the following:
<screen>driftfile /var/lib/chrony/drift
@@ -885,8 +885,8 @@ The <option>offline</option> option can be useful in
preventing systems from try
</orderedlist>
</para>
- <section
id="sect-Networking_Guide-Configuring_chrony_to_connect_and_disconnect">
- <title>Configuring chrony to Connect and Disconnect</title>
+ <section id="sect-Configuring_chrony_to_connect_and_disconnect">
+ <title>Configuring chrony To Connect And Disconnect</title>
<para>
Using your editor running as root, add the following to the
<filename>/etc/ppp/ip-up</filename> file:
<screen>
@@ -913,8 +913,8 @@ offline
</section>
- <section
id="sect-Networking_Guide-Setting_up_chrony_for_a_system_in_an_isolated_network">
- <title>Setting up chrony for a System in an Isolated Network</title>
+ <section
id="sect-Setting_up_chrony_for_a_system_in_an_isolated_network">
+ <title>Setting Up chrony For A System In An Isolated Network</title>
<para>
For a network that is never connected to the Internet, one computer is selected to
be the master timeserver. The other computers are either direct clients of the master, or
clients of clients. On the master, the drift file must be manually set with the average
rate of drift of the system clock. If the master is rebooted it will obtain the time from
surrounding systems and take an average to set its system clock. Thereafter it resumes
applying adjustments based on the drift file. The drift file will be updated automatically
when the <command>settime</command> command is used.
</para>
@@ -950,8 +950,8 @@ Where <systemitem
class="ipaddress">192.0.2.123</systemitem> is the address of t
</section>
-<section
id="sect-Networking_Guide-Using_chronyc_chronyc_to_control_cronyd">
- <title>Using chronyc to control cronyd</title>
+<section id="sect-Using_chronyc_chronyc_to_control_cronyd">
+ <title>Using chronyc To Control cronyd</title>
<para>
To make changes using the command line utility
<application>chronyc</application> in interactive mode, enter the following
command as root:
<screen>~]# chronyc</screen>
@@ -970,8 +970,8 @@ Where <systemitem
class="ipaddress">192.0.2.123</systemitem> is the address of t
</para>
</section>
-<section
id="sect-Networking_Guide-Using_chronyc_for_remote_administration">
-<title>Using chronyc for remote administration</title>
+<section id="sect-Using_chronyc_for_remote_administration">
+<title>Using chronyc For Remote Administration</title>
<para>
To configure <application>chrony</application> to connect to a remote
instance of <systemitem class="daemon">chronyd</systemitem>, issue a
command as root in the following format:
<screen>~]# <command>chronyc <option>-h</option>
<replaceable>hostname</replaceable></command></screen>
@@ -1001,7 +1001,7 @@ Note that commands issued at the
<application>chrony</application> command promp
</section>
<!--Topics, Reference-->
- <section id="sect-Networking_Guide-additional_resources">
+ <section id="sect-additional_resources">
<title>Additional Resources</title>
<para>