ntp.conf revision 1.15
1# $NetBSD: ntp.conf,v 1.15 2013/12/28 03:18:39 christos Exp $ 2# 3# NetBSD default Network Time Protocol (NTP) configuration file for ntpd 4 5# This file is intended to be both a usable default, and a Quick-Start 6# Guide. The directives and options listed here are not at all complete. 7# A great deal of additional documentation, including links to FAQS and 8# other guides, may be found on the official NTP web site, in particular 9# 10# http://www.ntp.org/documentation.html 11# 12 13# Process ID file, so that the daemon can be signalled from scripts 14 15pidfile /var/run/ntpd.pid 16 17# The correction calculated by ntpd(8) for the local system clock's 18# drift is stored here. 19 20driftfile /var/db/ntp.drift 21 22# Suppress the syslog(3) message for each peer synchronization change. 23 24logconfig -syncstatus 25 26# This will help minimize disruptions due to network congestion. Don't 27# do this if you configure only one server! 28 29tos minsane 2 30 31# Set the number of tries to register with mdns. 0 means never 32# 33mdnstries 0 34 35# New ntpd disables the ntpdc protocol by default, to re-enable uncomment 36# the following line 37# enable mode7 38 39# Hereafter should be "server" or "peer" statements to configure other 40# hosts to exchange NTP packets with. Peers should be selected in such 41# a way that the network path to them is symmetric (that is, the series 42# of links and routers used to get to the peer is the same one that the 43# peer uses to get back. NTP assumes such symmetry in its network delay 44# calculation. NTP will apply an incorrect adjustment to timestamps 45# received from the peer if the path is not symmetric. This can result 46# in clock skew (your system clock being maintained consistently wrong 47# by a certain amount). 48# 49# The best way to select symmetric peers is to make sure that the 50# network path to them is as short as possible (this reduces the chance 51# that there is more than one network path between you and your peer). 52# You can measure these distances with the traceroute(8) program. The 53# best place to start looking for NTP peers for your system is within 54# your own network, or at your Internet Service Provider (ISP). 55# 56# Ideally, you should select at least three other systems to talk NTP 57# with, for an "what I tell you three times is true" effect. 58# 59 60#peer an.ntp.peer.goes.here 61#server an.ntp.server.goes.here 62 63# Public servers from the pool.ntp.org project. Volunteer's servers 64# are dynamically assigned to the CNAMES below via DNS round-robin. 65# The pool.ntp.org project needs more volunteers! The only criteria to 66# join are a nailed-up connection and a static IP address. For details, 67# see the web page: 68# 69# http://www.pool.ntp.org/join.html 70# 71 72# Depending on the vagaries of DNS can occasionally pull in the same 73# server twice. The following CNAMES are guaranteed to be disjoint, at 74# least over some short interval. The following servers are allocated 75# to the NetBSD project. 76 77server 0.netbsd.pool.ntp.org 78server 1.netbsd.pool.ntp.org 79server 2.netbsd.pool.ntp.org 80server 3.netbsd.pool.ntp.org 81