4 # The contents of this file are subject to the terms of the
5 # Common Development and Distribution License (the "License").
6 # You may not use this file except in compliance with the License.
8 # You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
9 # or http://www.opensolaris.org/os/licensing.
10 # See the License for the specific language governing permissions
11 # and limitations under the License.
13 # When distributing Covered Code, include this CDDL HEADER in each
14 # file and include the License file at usr/src/OPENSOLARIS.LICENSE.
15 # If applicable, add the following below this CDDL HEADER, with the
16 # fields enclosed by brackets "[]" replaced with your own identifying
17 # information: Portions Copyright [yyyy] [name of copyright owner]
21 # Copyright (c) 2009, 2011, Oracle and/or its affiliates. All rights reserved.
23 # Since in general, all NTP servers can be NTP clients and vice
24 # versa, all of the information in the /etc/inet/ntp.client file
25 # applies to NTP server setup as well. However, a certain kind
26 # NTP server, called a Stratum 1 server, has one or more devices
27 # designed to provide very accurate time to the server. These
28 # devices are configured using the "server" keyword, just as the
29 # servers used by the client are, but instead of a hostname or
30 # IP address, a format resembling an IP address is used. The first
31 # two octets of "127.127" are used to designate that this
32 # line is referring to a clock and not an network NTP server.
33 # The next octet is used to designate which type of device is used.
34 # And the last octet is used to specify a unit number if more than
35 # one is used. Notice that the resulting number looks like the
36 # localhost address, it is not the same. The real localhost
37 # address (127.0.0.1) does not have the second octet of 127 as
38 # the hardware clock designator does.
40 # XType Device RefID Description
41 # -------------------------------------------------------
42 # 1 local LCL Undisciplined Local Clock
43 # 3 pst WWV PSTI/Traconex WWV/WWVH Receiver
44 # 4 wwvb WWVB Spectracom WWVB Receiver
45 # 5 true TRUE TrueTime GPS/GOES Receivers
46 # 6 irig IRIG IRIG Audio Decoder
47 # 7 chu CHU Scratchbuilt CHU Receiver
48 # 8 parse ---- Generic Reference Clock Driver
49 # 9 mx4200 GPS Magnavox MX4200 GPS Receiver
50 # 10 as2201 GPS Austron 2201A GPS Receiver
51 # 11 arbiter GPS Arbiter 1088A/B GPS Receiver
52 # 12 tpro IRIG KSI/Odetics TPRO/S IRIG Interface
53 # 13 leitch ATOM Leitch CSD 5300 Master Clock Controller
54 # 17 datum DATM Datum Precision Time System
55 # 18 acts ACTS NIST Automated Computer Time Service
56 # 19 heath WWV Heath WWV/WWVH Receiver
57 # 20 nmea GPS Generic NMEA GPS Receiver
59 # 22 atom PPS PPS Clock Discipline
60 # 26 hpgps GPS Hewlett Packard 58503A GPS Receiver
61 # 27 arc MSFa Arcron MSF Receiver
62 # 28 shm Shared memory driver
63 # 29 palisade Palisade
65 # 31 jupiter Jupiter GPS
66 # 32 chronolog Chronolog
67 # 33 dumbclock Dumbclock
72 # 38 hopfser HOPF Serial
78 # 44 neoclock4x NEOCLOCK 4X
80 # While all the current refclock drivers are configured and compiled,
81 # not all the actual hardware can be supported on all systems. The
82 # gpsvme driver can only be expected to work on systems with a VME
83 # bus. The WWV audio driver can only be used on systems with audio
86 # In general, refclock type 1, the LOCAL clock is not necessary and
87 # should not be configured. It should only be used when either there
88 # is some other process being used to synchronize the clock, such as
89 # with hardware with vendor provided drivers, or when it is desired
90 # that a server without access to a real NTP time source needs to
91 # act as a multicast or broadcast server. The LOCAL clock should not
92 # be configured as a "backup" to other external servers.
94 # Some of the devices have tuning parameters, called "fudge" factors,
95 # that can be set on the server line. See the ntpd documentation.