source: trunk/third/xntp/conf/grundoon.conf @ 10832

Revision 10832, 7.2 KB checked in by brlewis, 27 years ago (diff)
This commit was generated by cvs2svn to compensate for changes in r10831, which included commits to RCS files with non-trunk default branches.
RevLine 
[10831]1#
2# NTP configuration file (ntp.conf)
3# grundoon.udel.edu
4#
5# This machine can best be described as the kitchen sink. It has, in
6# addition to the baseboard tty ports ttya and ttyb, an 8-line
7# Serial/Parallel Interface (SPIF) with ports ttyz00 through ttyz07. The
8# configuration includes the following drivers, clock addresses and Unix
9# device names.
10#
11# Local Clock                   127.127.1.0     /dev/audio
12# PST 1020 WWV/WWVH Receiver    127.127.3.1     /dev/pst1
13# Spectracom 8170 WWVB Receiver 127.127.4.1     /dev/wwvb1
14# IRIG Audio Decoder            127.127.6.0     /dev/audio
15# Scratchbuilt CHU Receiver     127.127.7.1     /dev/chu1
16# NIST ACTS modem               127.127.18.1    /dev/acts1
17# Heath GC-1000 WWV Receiver    127.127.19.1    /dev/pst1
18# PPS Clock                     127.127.22.1    none
19#
20# This machine has the kernel modifications described in the README.kern
21# file, as well as the tty_clk, tty_chu and ppsclock streams modules.
22#
23# Spectracom 8170/Netclock-2 WWVB receiver. This receiver is equipped
24# with a 1-pps and IRIG outputs. The 1-pps signal is connected via the
25# ppsclock streams module and the carrier detect line of the CHU
26# receiver below (ttyb). The IRIG signal is connected via an attenuator
27# to the audio port (/dev/audio). The propagation delay computed from
28# geographical coordinates is 8.8 ms, while the receiver delay
29# calibrated at the factory is 17.3 ms, for a total delay of 26.1 ms.
30# This is confirmed within 0.1 ms at the 1-pps signal output using a
31# portable cesium clock. We add a fudge time1 of 3.5 ms so the driver
32# time agrees with the 1-pps signal to within 1 ms. The fudge flag4 is
33# set to cause the receiver to dump the quality table once each day to
34# the clockstats file.
35
36#
37#server 127.127.4.1             # /dev/wwvb1 -> /dev/ttyz03
38#fudge 127.127.4.1 time1 0.0035 flag4 1
39#
40# IRIG Audio Decoder. The IRGI signal of the Spectracom WWVB receiver is
41# connected to the audio codec via a resistor attenuator. We add a fudge
42# time1 of 3.5 ms so the driver agrees with the calibrated 1-pps signal
43# to within 0.1 ms. We also specify a reference ID of WWVB to indicate
44# the signal origin. Note the prefer keyword in the server line, which
45# favors this driver over all others that survive the clock selection
46# algorithm. See README.refclock for further insight on this feature.
47#
48server 127.127.6.0 prefer       # /dev/audio
49fudge 127.127.6.0 time1 0.0005 refid WWVB
50
51#
52# PST/Traconex 1020 WWV/WWVH Receier. The internal DIPswitches are set
53# as near as possible to the delays to WWV (8.8 ms) and WWVH (28.1 ms),
54# as computed from geographical coordinates. We add a fudge time1 of 5.9
55# ms so the driver time agrees with the 1-pps signal to within 1 ms for
56# WWV. We also set the stratum to 1, so this receiver will not normally
57# be selected, unless the primary WWVB receiver comes unstuck.
58#
59server 127.127.3.1              # /dev/pst1 -> ttyz05
60fudge 127.127.3.1 time1 0.0059 stratum 1
61
62#
63# Scratchbuilt CHU Receiver. The audio signal from a computer controlled
64# CHU receiver is connected to a gadget box, which contains a 103A modem
65# chip and level converter operating at 300 bps. The propagation delay
66# computed from geographical coordinates is 3.0 ms, which is the value
67# of the fudge time1 parameter. We add a fudge time2 of 9.9 ms so that
68# the driver time agrees with the 1-pps signal to within a few ms,
69# ordinarily the best possible with this receiver. The fudge flag3 is
70# set because the 1-pps signal happens to be connected vit the carrier
71# detect line on this port (ttyb). We also set the stratum to 1, so this
72# receiver will not normally be selected, unless the primary WWVB
73# receiver comes unstuck.
74#
75server 127.127.7.1              # /dev/chu1 -> /dev/ttyb
76fudge 127.127.7.1 time1 0.0030 time2 0.0099 flag3 1 stratum 1
77
78#
79# NIST Automated Computer Time Service. This driver calls a special
80# telephone number in Boulder, CO, to fetch the time directly from the
81# NIST cesium farm. The details of the complicated calling program are
82# in the README.refclock file. The Practical Peripherals 9600SA modem
83# does not work correctly with the ACTS echo-delay scheme for
84# automatically calculating the propagation delay, so the fudge flag2 is
85# set to disable the feature. Instead, we add a fudge time1 of 65.0 ms
86# so that the driver time agrees with th e1-pps signal to within 1 ms.
87# The phone command specifies three alternate telephone numbers,
88# including AT modem command prefix, which will be tried one after the
89# other at each measurement attempt. In this case, a cron job is used to
90# set fudge flag1, causing a measurement attempt, every six hours.
91#
92server 127.127.18.1             # /dev/acts1 -> /dev/ttyz00
93fudge 127.127.18.1 time1 0.0650 flag2 1
94phone atdt13034944774 atdt13034944785 atdt13034944774
95
96#
97# Heath GC-1000 Most Accurate Clock. This is a WWV receiver with a
98# claimed accuracy better than 100 ms under "hi spec" conditions, but
99# such conditions are not frequent. The propagation delay DIPswitchs are
100# set to 9 ms, as close as possible to the 8.8 ms computed from
101# geographical coordinates. We add a fudge time2 of 40.0 ms so that the
102# driver time agrees with the 1-pps signal to within 50 ms, ordinarily
103# the best possible with this receiver. We also set the stratum to 1, so
104# this receiver will not normally be selected, unless the primary WWVB
105# receiver comes unstuck.
106#
107server 127.127.19.1             # /dev/heath1 -> ttyz07
108fudge 127.127.19.1 time1 0.040 stratum 1
109
110#
111# Undisciplined Local Clock. This is a fake driver intended for backup
112# and when no outside source of synchronized time is available. The
113# default stratum is usually 3, but in this case we elect to use stratum
114# 0. Since the server line does not have the prefer keyword, this driver
115# is never used for synchronization, unless no other other
116# synchronization source is available. In case the local host is
117# controlled by some external source, such as an external oscillator or
118# another protocol, the prefer keyword would cause the local host to
119# disregard all other synchronization sources, unless the kernel
120# modifications are in use and declare an unsynchronized condition.
121#
122server 127.127.1.0              # local clock
123fudge 127.127.1.0 stratum 0
124
125#
126# PPS Clock. This driver is used to capture a 1-pps signal when the PPS
127# kernel modifications are not in use. It can be configured for the
128# tty_clk or ppsclock streams module or no module at all, assuming the
129# RS232 connector is properly wired. Normally, the 1-pps signal is
130# generated by a radio clock, in this cast the Spectracom clock
131# 127.127.4.1 also configured for this host. When used this way, the
132# associated radio clock normally has the prefer keyword in the serve
133# command line. The PPS driver then will be selected only if the prefer
134# peer is operating within nominal error bounds. See the README.refclock
135# file for further details.
136#
137#server 127.127.22.1            # pps clock
138
139#
140# Miscellaneous stuff. We enable authentication in order to prevent
141#
142driftfile /etc/ntp.drift        # path for drift file
143statsdir /grundoon/ntpstats/    # directory for statistics files
144filegen peerstats file peerstats type day enable
145filegen loopstats file loopstats type day enable
146filegen clockstats file clockstats type day enable
147
148#
149# Authentication stuff
150#
151keys /usr/local/etc/ntp.keys    # path for keys file
152trustedkey 1 2 3 4 5 6 14 15    # define trusted keys
153requestkey 15                   # key (7) for accessing server variables
154controlkey 15                   # key (6) for accessing server variables
Note: See TracBrowser for help on using the repository browser.