NetBSD/etc/ntp.conf

78 lines
2.6 KiB
Plaintext
Raw Normal View History

# $NetBSD: ntp.conf,v 1.6 2003/12/07 16:01:00 fredb Exp $
#
# NetBSD default Network Time Protocol (NTP) configuration file
# for ntpd
# Process ID file, so that the daemon can be signalled from scripts
2001-03-08 22:05:13 +03:00
pidfile /var/run/ntpd.pid
# The correction calculated by ntpd(8) for the local system clock's
# drift is stored here
2001-03-08 22:05:13 +03:00
driftfile /var/db/ntp.drift
# suppress the syslog(3) message for each peer synchronization change
2001-03-08 22:05:13 +03:00
logconfig -syncstatus
2003-12-07 18:56:30 +03:00
# This will help minimize disruptions due to network congestion. Don't
# do this if you configure only one server!
tos minsane 2
# Hereafter should be "server" or "peer" statements to configure
# other hosts to exchange NTP packets with. Peers should be selected
# in such a way that the network path to them is symmetric (that is,
# the series of links and routers used to get to the peer is the same
# one that the peer uses to get back. NTP assumes such symmetry
# in its network delay calculation. NTP will apply an incorrect
# adjustment to timestamps received from the peer if the path is not
# symmetric. This can result in clock skew (your system clock being
# maintained consistently wrong by a certain amount).
#
# The best way to select symmetric peers is to make sure that the
# network path to them is as short as possible (this reduces the
# chance that there is more than one network path between you and
# your peer). You can measure these distances with the traceroute(8)
# program. The best place to start looking for NTP peers for your
# system is within your own network, or at your Internet Service
# Provider (ISP).
#
# Ideally, you should select at least three other systems to talk
# NTP with, for an "what I tell you three times is true" effect.
#
2001-03-08 22:05:13 +03:00
#peer an.ntp.peer.goes.here
#server an.ntp.server.goes.here
# Public servers from the pool.ntp.org project. Volunteer's servers
# are dynamically assigned to the CNAMES below via DNS round-robin.
# The pool.ntp.org project needs more volunteers! The only criteria to
# join are a nailed-up connection and a static IP address. For details,
# see the web page:
#
# http://www.pool.ntp.org/
#
# The country codes can help you find servers that are net-wise close.
# As explained above, closer is better...
# Northern U.S.A
#server ca.pool.ntp.org
#server us.pool.ntp.org
#server us.pool.ntp.org
# Northern Europe
#server de.pool.ntp.org
#server de.pool.ntp.org
#server dk.pool.ntp.org
# Depending on the vagaries of DNS can occasionally pull in the same
# server twice. The following CNAMES are guaranteed to be disjoint, at
# least over some short interval.
server 0.pool.ntp.org
server 1.pool.ntp.org
server 2.pool.ntp.org