commit 1d9d24d94ff9cfbbe6af3ee2e9800160c1058600
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Mon Jul 1 14:28:36 2013 +0200
Improving the explanation of rtcsync directive & 11 minute mode.
en-US/Configuring_NTP_using_the_Chrony_suite.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Configuring_NTP_using_the_Chrony_suite.xml
b/en-US/Configuring_NTP_using_the_Chrony_suite.xml
index 57c11c0..b903cb9 100644
--- a/en-US/Configuring_NTP_using_the_Chrony_suite.xml
+++ b/en-US/Configuring_NTP_using_the_Chrony_suite.xml
@@ -866,7 +866,7 @@ This is the estimated error bounds on Freq (again in parts per
million).
</para>
<para>
- 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.
+ 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, the <application>rtcsync</application> directive is present in the
<filename>/etc/chrony.conf</filename> file. This will inform the kernel the
system clock is kept synchronized and the kernel will update the real-time clock every 11
minutes.
</para>
</section>
</section>
Show replies by date