commit 6edc62aa0ec67c2e5df3e5516eb32d3b1c8ca88e
Author: Stephen Wadeley <swadeley at redhat.com>
Date: Sat Jun 29 18:47:40 2013 +0200
Grouping sections as structure was too "flat"
en-US/Configuring_NTP_using_the_Chrony_suite.xml | 34 ++++++++++++++++++++-
1 files changed, 32 insertions(+), 2 deletions(-)
---
diff --git a/en-US/Configuring_NTP_using_the_Chrony_suite.xml b/en-US/Configuring_NTP_using_the_Chrony_suite.xml
index a7914a3..57c11c0 100644
--- a/en-US/Configuring_NTP_using_the_Chrony_suite.xml
+++ b/en-US/Configuring_NTP_using_the_Chrony_suite.xml
@@ -20,7 +20,6 @@ There is a choice between the daemons <systemitem class="daemon">ntpd</systemite
<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>
@@ -111,7 +110,13 @@ Things <systemitem class="daemon">ntpd</systemitem> can do that <systemitem clas
</listitem>
</itemizedlist>
</section>
-<section id="sect-Understanding_chronyd">
+ </section>
+ <section id="sect-Understanding_chrony_and-its_configuration">
+ <title>Understanding chrony And Its Configuration</title>
+ <para>
+
+ </para>
+ <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>.
@@ -484,9 +489,17 @@ chronyc> <command>password HEX:A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</command
</simplelist>.
</para>
</section>
+</section>
<!--Topics, Tasks:-->
+ <section id="sect-Using_chrony">
+ <title>Using chrony</title>
+ <para>
+
+ </para>
+
+
<section id="sect-Checking_if_chrony_is_installed">
<title>Checking If chrony Is Installed</title>
<para>
@@ -856,6 +869,14 @@ This is the estimated error bounds on Freq (again in parts per million).
In &MAJOROS;, the 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. By default, <application>rtcsync</application> will inform the kernel the system clock is synchronized and the kernel will update the real-time clock in 11 minute intervals.
</para>
</section>
+</section>
+
+<section id="sect-Setting_up_chrony_for_different_environments">
+ <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>
@@ -949,6 +970,14 @@ Where <systemitem class="ipaddress">192.0.2.123</systemitem> is the address of t
</para>
</section>
+</section>
+
+<section id="sect-Using_chronyc">
+ <title>Using chronyc</title>
+ <para>
+
+ </para>
+
<section id="sect-Using_chronyc_chronyc_to_control_cronyd">
<title>Using chronyc To Control cronyd</title>
@@ -999,6 +1028,7 @@ Note that commands issued at the <application>chrony</application> command promp
</para>
</section>
+</section>
<!--Topics, Reference-->
<section id="sect-additional_resources">