Index: examples/chrony.conf.example3
--- examples/chrony.conf.example3.orig
+++ examples/chrony.conf.example3
@@ -1,7 +1,7 @@
 #######################################################################
 #
 # This is an example chrony configuration file.  You should copy it to
-# /etc/chrony.conf after uncommenting and editing the options that you
+# ${SYSCONFDIR}/chrony.conf after uncommenting and editing the options that you
 # want to enable.  The more obscure options are not included.  Refer
 # to the documentation for these.
 #
@@ -81,12 +81,12 @@
 # immediately so that it doesn't gain or lose any more time.  You
 # generally want this, so it is uncommented.
 
-driftfile /var/lib/chrony/drift
+driftfile ${VARBASE}/db/chrony/drift
 
 # If you want to enable NTP authentication with symmetric keys, you will need
 # to uncomment the following line and edit the file to set up the keys.
 
-! keyfile /etc/chrony.keys
+! keyfile ${SYSCONFDIR}/chrony.keys
 
 # If you specify an NTP server with the nts option to enable authentication
 # with the Network Time Security (NTS) mechanism, or enable server NTS with
@@ -94,15 +94,15 @@ driftfile /var/lib/chrony/drift
 # allow the client/server to save the NTS keys and cookies in order to reduce
 # the number of key establishments (NTS-KE sessions).
 
-ntsdumpdir /var/lib/chrony
+ntsdumpdir ${VARBASE}/db/chrony
 
 # If chronyd is configured to act as an NTP server and you want to enable NTS
 # for its clients, you will need a TLS certificate and private key.  Uncomment
 # and edit the following lines to specify the locations of the certificate and
 # key.
 
-! ntsservercert /etc/.../nts-server.crt
-! ntsserverkey /etc/.../nts-server.key
+! ntsservercert ${SYSCONFDIR}/.../nts-server.crt
+! ntsserverkey ${SYSCONFDIR}/.../nts-server.key
 
 # chronyd can save the measurement history for the servers to files when
 # it exits.  This is useful in 2 situations:
@@ -119,14 +119,14 @@ ntsdumpdir /var/lib/chrony
 #
 # Uncomment the following line to use this.
 
-! dumpdir /var/lib/chrony
+! dumpdir ${VARBASE}/db/chrony
 
 # chronyd writes its process ID to a file.  If you try to start a second
 # copy of chronyd, it will detect that the process named in the file is
 # still running and bail out.  If you want to change the path to the PID
 # file, uncomment this line and edit it.  The default path is shown.
 
-! pidfile /var/run/chrony/chronyd.pid
+! pidfile ${VARBASE}/run/chrony/chronyd.pid
 
 # The system timezone database usually comes with a list of leap seconds and
 # corresponding TAI-UTC offsets.  chronyd can use it to set the offset of the
@@ -167,7 +167,7 @@ ntsdumpdir /var/lib/chrony
 # produce some graphs of your system's timekeeping performance, or you
 # need help in debugging a problem.
 
-! logdir /var/log/chrony
+! logdir ${VARBASE}/log/chrony
 ! log measurements statistics tracking
 
 # If you have real time clock support enabled (see below), you might want
@@ -291,7 +291,7 @@ ntsdumpdir /var/lib/chrony
 # You need to have 'enhanced RTC support' compiled into your Linux
 # kernel.  (Note, these options apply only to Linux.)
 
-! rtcfile /var/lib/chrony/rtc
+! rtcfile ${VARBASE}/db/chrony/rtc
 
 # Your RTC can be set to keep Universal Coordinated Time (UTC) or local
 # time.  (Local time means UTC +/- the effect of your timezone.)  If you
