172N/A# The contents of this file are subject to the terms of the
172N/A# Common Development and Distribution License (the "License").
172N/A# You may not use this file except in compliance with the License.
172N/A# See the License for the specific language governing permissions
172N/A# and limitations under the License.
172N/A# When distributing Covered Code, include this CDDL HEADER in each
172N/A# If applicable, add the following below this CDDL HEADER, with the
172N/A# fields enclosed by brackets "[]" replaced with your own identifying
172N/A# information: Portions Copyright [yyyy] [name of copyright owner]
172N/A# Copyright (c) 2009, 2011, Oracle
and/or its affiliates. All rights reserved.
172N/A# If you want to configure your client to listen for multicast, uncommnet
172N/A# this line. This should only be used for casual time keeping, like keeping
172N/A# a desktop system in sync.
172N/A#multicastclient 224.0.1.1
172N/A# To configure NTP servers, replace the server_name with either the IP address
172N/A# or hostname of the server you wish to use. If you just want to keep the time
172N/A# in a causual way, one server may be enough for you. If you wish to keep it
172N/A# to a more accurate level, 3 or more is recommended. Do not choose 2, because
172N/A# 2 servers is an unstable configuration. By the same token 3 is only acceptable
172N/A# if all are always available, since when a single one reboots or otherwise
172N/A# becomes unavailable, you have just 2.
172N/A# For a list of Internet NTP servers see
172N/A# If you use this list, be sure to read, understand and abide by the rules
172N/A# each server has published for accessing themselves.
172N/A# There is also a DNS round-robin pool of public access NTP servers. The
172N/A# Please consider adding your own servers to the pool if possible.
172N/A# Many ISP's also provide NTP servers for use by their customers.
172N/Aserver server_name iburst
172N/A# Always configure the drift file. It can take days for ntpd to completely
172N/A# stabilize and without the drift file, it has to start over on a reboot
172N/A# It is always wise to configure at least the loopstats and peerstats files.
172N/A# Otherwise when ntpd does something you don't expect there is no way to
172N/Afilegen peerstats file peerstats type day enable
172N/Afilegen loopstats file loopstats type day enable
172N/A# To track the events regarding the system clock, the protostats file can be useful
172N/A#filegen protostats file protostats type day enable
172N/A# To see the current state of the crypto authentication protocols, enable the
172N/A#filegen cryptostats file cryptostats type day enable
172N/A# The clockstats files are only useful if a hardware reference clock is
172N/A#filegen clockstats file clockstats type day enable
172N/A# The sysstats and rawstats output might be useful in debugging.
172N/A#filegen sysstats file sysstats type day enable
172N/A#filegen rawstats file rawstats type day enable
172N/A# The timingstats file is probably not useful at all. It is designed for
172N/A# perfomance debugging by the developers of NTP.
172N/A#filegen timingstats file timingstats type day enable
172N/A# There are several types on authentication supported by NTP. The easiest
172N/A# to use is a set of passwords, called "keys". They should be stored
172N/A# assigned to certain types of trust levels. See ntpd(1m) for more
172N/A# information on setting up key.
172N/A# To configure leap seconds processing, download the latest NIST leap seconds
172N/A# file. Without this file, NTP will still be able to accept leap announcements
172N/A# from its upstream sources. If this file exists and is less than 6 months old
172N/A# then the contents of this file will take precedence over the upstream servers.