Home | History | Annotate | Line # | Download | only in etc
ntp.conf revision 1.8 
      1 # $NetBSD: ntp.conf,v 1.8 2003/12/07 16:11:58 fredb 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 documention, 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 
     15 pidfile		/var/run/ntpd.pid
     16 
     17 # The correction calculated by ntpd(8) for the local system clock's
     18 # drift is stored here.
     19 
     20 driftfile	/var/db/ntp.drift
     21 
     22 # Suppress the syslog(3) message for each peer synchronization change.
     23 
     24 logconfig	-syncstatus
     25 
     26 # This will help minimize disruptions due to network congestion. Don't
     27 # do this if you configure only one server!
     28 
     29 tos		minsane 2
     30 
     31 # Hereafter should be "server" or "peer" statements to configure other
     32 # hosts to exchange NTP packets with. Peers should be selected in such
     33 # a way that the network path to them is symmetric (that is, the series
     34 # of links and routers used to get to the peer is the same one that the
     35 # peer uses to get back. NTP assumes such symmetry in its network delay
     36 # calculation. NTP will apply an incorrect adjustment to timestamps
     37 # received from the peer if the path is not symmetric. This can result
     38 # in clock skew (your system clock being maintained consistently wrong
     39 # by a certain amount).
     40 #
     41 # The best way to select symmetric peers is to make sure that the
     42 # network path to them is as short as possible (this reduces the chance
     43 # that there is more than one network path between you and your peer).
     44 # You can measure these distances with the traceroute(8)  program. The
     45 # best place to start looking for NTP peers for your system is within
     46 # your own network, or at your Internet Service Provider (ISP).
     47 #
     48 # Ideally, you should select at least three other systems to talk NTP
     49 # with, for an "what I tell you three times is true" effect.
     50 #
     51 
     52 #peer		an.ntp.peer.goes.here
     53 #server		an.ntp.server.goes.here
     54 
     55 # Public servers from the pool.ntp.org project. Volunteer's servers
     56 # are dynamically assigned to the CNAMES below via DNS round-robin.
     57 # The pool.ntp.org project needs more volunteers! The only criteria to
     58 # join are a nailed-up connection and a static IP address. For details,
     59 # see the web page:
     60 #
     61 #	http://www.pool.ntp.org/ 
     62 #
     63 
     64 # The country codes can help you find servers that are net-wise close.
     65 # As explained above, closer is better...
     66 
     67 # Northern U.S.A
     68 #server		ca.pool.ntp.org
     69 #server		us.pool.ntp.org
     70 #server		us.pool.ntp.org
     71 
     72 # Northern Europe
     73 #server		de.pool.ntp.org
     74 #server		de.pool.ntp.org
     75 #server		dk.pool.ntp.org
     76 
     77 # Depending on the vagaries of DNS can occasionally pull in the same
     78 # server twice. The following CNAMES are guaranteed to be disjoint, at
     79 # least over some short interval.
     80 
     81 server		0.pool.ntp.org
     82 server		1.pool.ntp.org
     83 server		2.pool.ntp.org
     84