Line 0
Link Here
|
|
|
1 |
--- examples/chrony.conf.example3.orig 2015-10-19 09:18:37 UTC |
2 |
+++ examples/chrony.conf.example3 |
3 |
@@ -1,7 +1,7 @@ |
4 |
####################################################################### |
5 |
# |
6 |
# This is an example chrony configuration file. You should copy it to |
7 |
-# /etc/chrony.conf after uncommenting and editing the options that you |
8 |
+# /usr/local/etc/chrony.conf after uncommenting and editing the options that you |
9 |
# want to enable. The more obscure options are not included. Refer |
10 |
# to the documentation for these. |
11 |
# |
12 |
@@ -47,7 +47,9 @@ |
13 |
! server bar.example.net iburst |
14 |
! server baz.example.net iburst |
15 |
|
16 |
-! pool pool.ntp.org iburst |
17 |
+# This is a reasonable default setting to have on in typical cases for |
18 |
+# a workstation with a full-time internet connection: |
19 |
+pool 0.freebsd.pool.ntp.org iburst |
20 |
|
21 |
# However, for dial-up use you probably want these instead. The word |
22 |
# 'offline' means that the server is not visible at boot time. Use |
23 |
@@ -58,7 +60,7 @@ |
24 |
! server bar.example.net offline |
25 |
! server baz.example.net offline |
26 |
|
27 |
-! pool pool.ntp.org offline |
28 |
+! pool 0.freebsd.pool.ntp.org offline |
29 |
|
30 |
# You may want to specify NTP 'peers' instead. If you run a network |
31 |
# with a lot of computers and want several computers running chrony to |
32 |
@@ -93,12 +95,12 @@ |
33 |
# immediately so that it doesn't gain or lose any more time. You |
34 |
# generally want this, so it is uncommented. |
35 |
|
36 |
-driftfile /var/lib/chrony/drift |
37 |
+driftfile /var/db/chrony/drift |
38 |
|
39 |
# If you want to enable NTP authentication with symmetric keys, you will need |
40 |
# to uncomment the following line and edit the file to set up the keys. |
41 |
|
42 |
-! keyfile /etc/chrony.keys |
43 |
+! keyfile /usr/local/etc/chrony.keys |
44 |
|
45 |
# chronyd can save the measurement history for the servers to files when |
46 |
# it it exits. This is useful in 2 situations: |
47 |
@@ -116,7 +118,7 @@ driftfile /var/lib/chrony/drift |
48 |
# Enable these two options to use this. |
49 |
|
50 |
! dumponexit |
51 |
-! dumpdir /var/lib/chrony |
52 |
+! dumpdir /var/db/chrony |
53 |
|
54 |
# chronyd writes its process ID to a file. If you try to start a second |
55 |
# copy of chronyd, it will detect that the process named in the file is |
56 |
@@ -145,6 +147,10 @@ driftfile /var/lib/chrony/drift |
57 |
# only need this if you really enjoy looking at the logs, you want to |
58 |
# produce some graphs of your system's timekeeping performance, or you |
59 |
# need help in debugging a problem. |
60 |
+# |
61 |
+# If you enable logging, you may want to add an entry to a log rotation |
62 |
+# utility's configuration (e.g., newsyslog(8)). 'chronyc cyclelogs' |
63 |
+# should be used to signal chronyd that a log file has been renamed. |
64 |
|
65 |
! logdir /var/log/chrony |
66 |
! log measurements statistics tracking |
67 |
@@ -259,7 +265,7 @@ driftfile /var/lib/chrony/drift |
68 |
# You need to have 'enhanced RTC support' compiled into your Linux |
69 |
# kernel. (Note, these options apply only to Linux.) |
70 |
|
71 |
-! rtcfile /var/lib/chrony/rtc |
72 |
+! rtcfile /var/db/chrony/rtc |
73 |
|
74 |
# Your RTC can be set to keep Universal Coordinated Time (UTC) or local |
75 |
# time. (Local time means UTC +/- the effect of your timezone.) If you |