ports/net/chrony/files/patch-examples_chrony.conf.example3
Rodrigo Osorio cc3c5867f4 Makes the NSS dependency explicit, and perform cleanup
Bump PORTREVISION

Before this patch if nss is installed when crony is built, there's a silent lib
dependency on nss, and if nss is subsequently uninstalled chrony breaks.

NSS is now turned on by default adding support for a number of more modern
hashing algorithms than md5.

Cleanup:
 - --infodir is not a valid configure option (since 2.3 I think)
 - USES=localbase instead of LDFLAGS
 - add explicit --without-tomcrypt [1]
 - add support for passing chronyd_flags to chronyd in rc.d script
 - fix some hard-coded /usr/local in examples

PR:		217691
Submitted by:	John Hein <z7dr6ut7gs@snkmail.com>
Approved by:	Yonas Yanfa <yonas@fizk.net> (maintainer)
2017-11-18 22:41:34 +00:00

66 lines
2.6 KiB
Text

--- examples/chrony.conf.example3.orig 2017-01-31 10:22:11 UTC
+++ 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
+# %%PREFIX%%/etc/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.
#
@@ -31,7 +31,9 @@
! server bar.example.net iburst
! server baz.example.net iburst
-! pool pool.ntp.org iburst
+# This is a reasonable default setting to have on in typical cases for
+# a workstation with a full-time internet connection:
+pool 0.freebsd.pool.ntp.org iburst
#######################################################################
### AVOIDING POTENTIALLY BOGUS CHANGES TO YOUR CLOCK
@@ -65,12 +67,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 /var/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 %%PREFIX%%/etc/chrony.keys
# chronyd can save the measurement history for the servers to files when
# it it exits. This is useful in 2 situations:
@@ -88,7 +90,7 @@ driftfile /var/lib/chrony/drift
# Enable these two options to use this.
! dumponexit
-! dumpdir /var/lib/chrony
+! dumpdir /var/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
@@ -117,6 +119,10 @@ driftfile /var/lib/chrony/drift
# only need this if you really enjoy looking at the logs, you want to
# produce some graphs of your system's timekeeping performance, or you
# need help in debugging a problem.
+#
+# If you enable logging, you may want to add an entry to a log rotation
+# utility's configuration (e.g., newsyslog(8)). 'chronyc cyclelogs'
+# should be used to signal chronyd that a log file has been renamed.
! logdir /var/log/chrony
! log measurements statistics tracking
@@ -253,7 +259,7 @@ driftfile /var/lib/chrony/drift
# 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 /var/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