[system-administrators-guide] Corrected all titles to follow the same rules.
jhradile
jhradile at fedoraproject.org
Mon Jul 1 12:48:47 UTC 2013
commit d456e49b25cfba363ebe2fc92557595bb1d8ba4d
Author: Jaromir Hradilek <jhradilek at redhat.com>
Date: Mon Jul 1 14:41:51 2013 +0200
Corrected all titles to follow the same rules.
en-US/Configuring_NTP_using_the_Chrony_suite.xml | 32 +++++++++++-----------
1 files changed, 16 insertions(+), 16 deletions(-)
---
diff --git a/en-US/Configuring_NTP_using_the_Chrony_suite.xml b/en-US/Configuring_NTP_using_the_Chrony_suite.xml
index 0425fec..48c33fe 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-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>
@@ -16,13 +16,13 @@
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-Introduction_to_the_chrony_suite">
- <title>Introduction To The chrony Suite</title>
+ <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 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:
@@ -112,7 +112,7 @@ Things <systemitem class="daemon">ntpd</systemitem> can do that <systemitem clas
</section>
</section>
<section id="sect-Understanding_chrony_and-its_configuration">
- <title>Understanding chrony And Its Configuration</title>
+ <title>Understanding chrony and Its Configuration</title>
<para>
</para>
@@ -130,7 +130,7 @@ Things <systemitem class="daemon">ntpd</systemitem> can do that <systemitem clas
</section>
<section id="sect-Understanding_the_chrony_configuration_commands">
- <title>Understanding The chrony Configuration Commands</title>
+ <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#Configuration-file</citetitle>
<variablelist>
@@ -409,7 +409,7 @@ Not all real-time clocks are supported as their code system-specific.
</section>
<section id="sect-Security_with_chronyc">
- <title>Security With chronyc</title>
+ <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:
@@ -501,7 +501,7 @@ chronyc> <command>password HEX:A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</command
<section id="sect-Checking_if_chrony_is_installed">
- <title>Checking If chrony Is Installed</title>
+ <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>
@@ -520,7 +520,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>
@@ -556,7 +556,7 @@ chronyd.service - NTP client/server
<section id="sect-Checking_if_chrony_is_synchronized">
- <title>Checking If chrony Is Synchronized</title>
+ <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>
@@ -855,7 +855,7 @@ This is the estimated error bounds on Freq (again in parts per million).
</section>
<section id="sect-Adjusting-the-System_Clock">
- <title>Manualy Adjusting The System Clock</title>
+ <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>
@@ -872,14 +872,14 @@ This is the estimated error bounds on Freq (again in parts per million).
</section>
<section id="sect-Setting_up_chrony_for_different_environments">
- <title>Setting up chrony For Different Environments</title>
+ <title>Setting Up chrony for Different Environments</title>
<para>
</para>
<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>
+ <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
@@ -907,7 +907,7 @@ The <option>offline</option> option can be useful in preventing systems from try
</para>
<section id="sect-Configuring_chrony_to_connect_and_disconnect">
- <title>Configuring chrony To Connect And Disconnect</title>
+ <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>
@@ -935,7 +935,7 @@ offline
<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>
+ <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>
@@ -980,7 +980,7 @@ Where <systemitem class="ipaddress">192.0.2.123</systemitem> is the address of t
<section id="sect-Using_chronyc_chronyc_to_control_cronyd">
- <title>Using chronyc To Control cronyd</title>
+ <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>
@@ -1000,7 +1000,7 @@ Where <systemitem class="ipaddress">192.0.2.123</systemitem> is the address of t
</section>
<section id="sect-Using_chronyc_for_remote_administration">
-<title>Using chronyc For Remote Administration</title>
+<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>
More information about the docs-commits
mailing list