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
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.
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