From d631d7e81f5e703658c35f4be39007b11b9217c9 Mon Sep 17 00:00:00 2001
From: Miroslav Lichvar <mlichvar@redhat.com>
Date: Tue, 1 Jul 2014 12:50:13 +0200
Subject: [PATCH] doc: use iburst option in examples

---
 chrony.conf.5.in | 10 ++++++----
 chrony.texi.in   | 20 +++++++++++---------
 2 files changed, 17 insertions(+), 13 deletions(-)

diff --git a/chrony.conf.5.in b/chrony.conf.5.in
index 47aca50..161ad13 100644
--- a/chrony.conf.5.in
+++ b/chrony.conf.5.in
@@ -24,11 +24,13 @@ However, you will probably want to include some of the other directives
 described in detail in the documentation supplied with the distribution
 (\fIchrony.txt\fR and \fIchrony.texi\fR). The following directives may be
 particularly useful : `driftfile', `generatecommandkey', `keyfile', `makestep'.
-The smallest useful configuration file would look something like
+Also, the `iburst' server option is useful to speed up the initial
+synchronization. The smallest useful configuration file would look something
+like
 
-     server a.b.c
-     server d.e.f
-     server g.h.i
+     server a.b.c iburst
+     server d.e.f iburst
+     server g.h.i iburst
      keyfile @SYSCONFDIR@/chrony.keys
      generatecommandkey
      driftfile @CHRONYVARDIR@/drift
diff --git a/chrony.texi.in b/chrony.texi.in
index d4bd2e8..e363777 100644
--- a/chrony.texi.in
+++ b/chrony.texi.in
@@ -434,12 +434,13 @@ Now that the software is successfully installed, the next step is to
 set up a configuration file.  The default location of the file
 is @file{@SYSCONFDIR@/chrony.conf}.  Suppose you want to use public NTP
 servers from the pool.ntp.org project as your time reference.  A
-minimal working configuration file could be
+minimal useful configuration file could be
 
 @example
-server 0.pool.ntp.org
-server 1.pool.ntp.org
-server 2.pool.ntp.org
+server 0.pool.ntp.org iburst
+server 1.pool.ntp.org iburst
+server 2.pool.ntp.org iburst
+makestep 10 3
 @end example
 
 Then, @code{chronyd} can be run.
@@ -586,13 +587,14 @@ server g.h.i
 
 However, you will probably want to include some of the other directives
 described later.  The @code{driftfile} and @code{makestep} directives may be
-particularly useful.  The smallest useful configuration file would look
-something like
+particularly useful.  Also, the @code{iburst} server option is useful to speed
+up the initial synchronization.  The smallest useful configuration file would
+look something like
 
 @example
-server a.b.c
-server d.e.f
-server g.h.i
+server a.b.c iburst
+server d.e.f iburst
+server g.h.i iburst
 driftfile @CHRONYVARDIR@/drift
 makestep 10 3
 @end example