1 '\" te

     2 .\" CDDL HEADER START

     3 .\"

     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.

     7 .\"

     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.

    12 .\"

    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]

    18 .\"

    19 .\" CDDL HEADER END

    20 .\"

    21 .\" Copyright 2009 Sun Microsystems, Inc.  All rights reserved.

    22 .\" Use is subject to license terms.

    23 .\"

    24 .\" #ident	"@(#)ntpd.1m	1.1	09/05/17 SMI"

    25 .\"

    26 .TH "ntpd" "1M" "" "" "System Administration Commands"

    27 .SH NAME

    28 ntpd \- Network Time Protocol daemon Version 4

    29 .SH SYNOPSIS

    30 .LP

    31 .nf

    32 \fB/usr/lib/inet/ntpd\fR [\fB-46aAbdDgLmnNqvx\fR] [\fB-c\fR \fIconffile\fR]

    33     [\fB-f\fR \fIdriftfile\fR] [\fB-k\fR \fIkeyfile\fR] [\fB-l\fR \fIlogfile\fR] [\fB-p\fR \fIpidfile\fR]

    34     [\fB-P\fR \fIpriority\fR] [\fB-r\fR \fIbroadcastdelay\fR] [\fB-s\fR \fIstatsdir\fR]

    35     [\fB-t\fR \fItrustedkey\fR] [\fB-U\fR \fIinterface_update_time\fR]

    36 .fi

    37 

    38 .SH DESCRIPTION

    39 The \fBntpd\fR program is an operating system daemon that synchronises the system clock with remote NTP time servers or local reference clocks. It is a complete implementation of the Network Time Protocol (\fBNTP\fR) version 4, but also retains compatibility with version 3, as defined by \fIRFC 1305\fR, and versions 1 and 2, as defined by \fIRFC 1059\fR and \fIRFC 1119\fR, respectively.

    40 .SS How \fBNTP\fR Operates

    41 The \fBntpd\fR program operates by exchanging messages with one or more configured servers at designated intervals ranging from about one minute to about 17 minutes. When started, the program requires several exchanges while the algorithms accumulate and groom the data before setting the clock. The initial delay to set the clock can be reduced using options as described in the server options page  at file:///usr/share/doc/ntp/confopt.html.

    42 .LP

    43 When the machine is booted, the hardware time of day (TOD) chip is used to initialize the operating system time. After the machine has synchronized to a \fBNTP\fR server, the operating system corrects the chip from time to time. During the course of operation if for some reason the system time is more than 1000s offset from the server time, \fBntpd\fR assumes something must be terribly wrong and exits with a panic message to the system log. If it was started via SMF, the ntp service is placed into maintainance mode and must be cleared manually. The -g option overrides this check at startup and allows \fBntpd\fR to set the clock to the server time regardless of the chip time, but only once.

    44 .LP

    45 Under ordinary conditions, \fBntpd\fR slews the clock so that the time is effectively continuous and never runs backwards. If due to extreme network congestion an error spike exceeds the \fIstep threshold\fR (128ms by default), the spike is discarded. However, if the error persists for more than the \fIstepout threshold\fR (900s by default) the system clock is stepped to the correct value. In practice the need for a step is extremely rare and almost always the result of a hardware failure. With the -x option the step threshold is increased to 600s. Other options are available using the \fItinker\fR command as described in the miscellaneous options page at file:///usr/share/doc/ntp/miscopt.html.

    46 .LP

    47 The issues should be carefully considered before using these options. The maximum slew rate possible is limited to 500 parts-per-million (PPM) by the Unix kernel. As a result, the clock can take 2000s for each second the clock is outside the acceptable range. During this interval the clock will not be consistent with any other network clock and the system cannot be used for distributed applications that require correctly synchronized network time.

    48 .LP

    49 .SS Frequency Discipline

    50 The frequency file, usually called ntp.drift, contains the latest estimate of clock frequency. If this file does not exist when ntpd is started, it enters a special mode designed to measure the particular frequency directly. The measurement takes 15 minutes, after which the frequency is set and ntpd resumes normal mode where the time and frequency are continuously adjusted. The frequency file is updated at intervals of an hour or more depending on the measured clock stability.

    51 .SS Operating Modes

    52 The \fBntpd\fR daemon can operate in any of several modes, including symmetric active/passive, client/server broadcast/multicast and manycast, as described in the Association Management page at file:///usr/share/doc/ntp/assoc.html. It normally operates continuously while monitoring for small changes in frequency and trimming the clock for the ultimate precision. However, it can operate in a one-time mode where the time is set from an external server and frequency is set from a previously recorded frequency file. A broadcast/multicast or manycast client can discover remote servers, compute server-client propagation delay correction factors and configure itself automatically. This makes it possible to deploy a fleet of workstations without specifying configuration details specific to the local environment.

    53 .LP

    54 By default, \fBntpd\fR runs in continuous mode where each of possibly several external servers is polled at intervals determined by an intricate phase/frequency-lock feedback loop. The feedback loop measures the incidental roundtrip delay jitter and oscillator frequency wander and determines the best poll interval using a heuristic algorithm. Ordinarily, and in most operating environments, the state machine will start with 64s intervals and eventually increase in steps to 1024s. A small amount of random variation is introduced in order to avoid bunching at the servers. In addition, should a server become unreachable for some time, the poll interval is increased in steps to 1024s in order to reduce network overhead. In general it is best not to force \fBntpd\fR to use specific poll intervals, allowing it to choose the best intervals based its current needs and the quality of the available servers and the clock.

    55 .LP

    56 In some cases it may not be practical for \fBntpd\fR to run continuously. In the past a common workaround has been to run the \fBntpdate\fR program from a cron job at designated times. However, \fBntpdate\fR does not have the crafted signal processing, error checking and mitigation algorithms of \fBntpd\fR. The \fBntpd\fR daemon with -q option is intended to replace \fBntpdate\fR when used in this manner. Setting this option will cause \fBntpd\fR to exit just after setting the clock for the first time. The procedure for initially setting the clock is the same as in continuous mode; most applications will probably want to specify the iburst keyword with the server configuration command. With this keyword a volley of messages are exchanged to groom the data and the clock is set in about 10s. If nothing is heard after a couple of minutes, the daemon times out and exits. Eventually the \fBntpdate\fR program may be retired.

    57 .SS Kernel Clock Discipline

    58 The kernel supports a method specific to \fBntpd\fR to discipline the clock frequency. First, \fBntpd\fR is run in continuous mode with selected servers in order to measure and record the intrinsic clock frequency offset in the frequency file. It may take some hours for the frequency and offset to settle down. Then \fBntpd\fR is run in normal mode as required. At each startup, the frequency is read from the file and initializes the kernel frequency, thus avoiding the settling period.

    59 When the kernel discipline is in use, the system's clock is adjusted at each system tick and thus the system clock is always as accurate as possible. When the kernel discipline is not used the clock is adjusted once each second. It is important to delete the ntp.drift file before starting \fBntpd\fR if the intrinsic frequency might have changed, such as by a motherboard swap.

    60 .SS Poll Interval Control

    61 The \fBntpd\fR program includes an intricate clock discipline to reduce the network 

    62 load while maintaining a quality of synchronization consistent with the observed 

    63 jitter and wander. There are a number of ways to tailor the operation in order to enhance 

    64 accuracy by reducing the interval or to reduce network overhead by increasing it. However, the user is advised to carefully consider the consequences of changing the poll adjustment range from the default. It is not the case that shorter poll intervals will necessarily 

    65 lead to more accuracy. Most device drivers will not operate properly if the poll interval is less than 64 s and that the broadcast server and manycast client associations will also use the default, unless overridden. In general, it is best to let \fBntpd\fR determine the best polling interval.

    66 .LP

    67 In some cases involving dial up or toll services, it may be useful to increase the minimum interval to a few tens of minutes and maximum interval to a day or so. Under normal operation conditions, once the clock discipline loop has stabilized the interval will be increased in steps from the minimum to the maximum. However, this assumes the intrinsic clock frequency error is small enough for the discipline loop correct it. The capture range of the loop is 500 PPM at an interval of 64s decreasing by a factor of two for each doubling of interval. At a minimum of 1,024 s, for example, the capture range is only 31 PPM. 

    68 .SS The Huff-n'-Puff Filter

    69 In scenarios where a considerable amount of data are to be downloaded or uploaded over bandwidth limited links, timekeeping quality can be seriously degraded due to the different delays in the two directions. In many cases the apparent time errors are so large as to exceed the step threshold and a step correction can occur during and after the data transfer is in progress.

    70 .LP

    71 The huff-n'-puff filter is designed to correct the apparent time offset in these cases. It depends on knowledge of the propagation delay when no other traffic is present. The filter maintains a shift register that remembers the minimum delay over the most recent interval measured usually in hours. Under conditions of severe delay, the filter corrects the apparent offset using the sign of the offset and the difference between the apparent delay and minimum delay. The name of the filter reflects the negative (huff) and positive (puff) correction, which depends on the sign of the offset.

    72 .LP

    73 The filter is activated by the tinker command and huffpuff keyword, as described in the Miscellaneous Options page at file:///usr/share/doc/ntp/miscopt.html.

    74 .SS Leap Second Processing

    75 As provided by international agreement, an extra second is sometimes inserted in Coordinated Universal Time (UTC) at the end of a selected month, usually June or December. The National Institutes of Standards and Technology (NIST) provides an historic leapseconds file at time.nist.gov for retrieval via FTP. This file, usually called ntp-leapseconds.list, is copied into the /etc/inet directory and the leapfile configuration command then specifies the path to this file. At startup, ntpd reads it and initializes three leapsecond values: the NTP seconds at the next leap event, the offset of UTC relative to International Atomic Time (TAI) after the leap and the NTP seconds when the leapseconds file expires and should be retrieved again.

    76 .LP

    77 If a host does not have the leapsecond values, they can be obtained over the net using the Autokey security protocol. Ordinarily, the leapseconds file is installed on the primary servers and the values flow from them via secondary servers to the clients. When multiple servers are involved, the values with the latest expiration time are used.

    78 .LP

    79 If the latest leap is in the past, nothing further is done other than to install the TAI offset. If the leap is in the future less than 28 days, the leap warning bits are set. If in the future less than 23 hours, the kernel is armed to insert one second at the end of the current day. Additional details are in the The NTP Timescale and Leap Seconds white paper at http://www.eecis.udel.edu/~mills/leap.html.

    80 .LP

    81 If none of the above provisions are available, dsependent servers and clients tally the leap warning bits of surviving servers and reference clocks. When a majority of the survivors show warning, a leap is programmed at the end of the current month. During the month and day of insertion, they operate as above. In this way the leap is is propagated at all dependent servers and clients.

    82 .LP

    83 .SH OPTIONS

    84 .TP

    85 .BR \-4 ", " \--ipv4

    86 Force DNS resolution of following host names on the command line

    87 to the IPv4 namespace. Cannot be used with the \fB--ipv6\fR option.

    88 .TP

    89 .BR \-6 ", " \--ipv6

    90 Force DNS resolution of following host names on the command line

    91 to the IPv6 namespace. Cannot be used with the \fB--ipv6\fR option.

    92 .TP

    93 .BR \-a ", " \--authreq

    94 Require cryptographic authentication for broadcast client,

    95 multicast client and symmetric passive associations.

    96 This is the default.

    97 This option must not appear with authnoreq option.

    98 .TP

    99 .BR \-A ", " \--authnoreq

   100 Do not require cryptographic authentication for broadcast client,

   101 multicast client and symmetric passive associations.

   102 This is almost never a good idea. This option must not appear with the authreq option.

   103 .TP

   104 .BR \-b ", " \--bcastsync

   105 Enable the client to sync to broadcast servers.

   106 .sp

   107 .TP

   108 .BR \-c " \fIstring\fP, " \--configfile "=" \fIstring\fP

   109 The name and path of the configuration file,

   110 /etc/inet/ntp.conf by default.

   111 .TP

   112 .BR \-d ", " \--debug-level

   113 Increase output debug message level.

   114 This option may appear an unlimited number of times.

   115 .TP

   116 .BR \-D " \fIstring\fP, " \--set-debug-level "=" \fIstring\fP

   117 Set the output debugging level.  Can be supplied multiple times,

   118 but each overrides the previous value(s).

   119 .TP

   120 .BR \-f " \fIstring\fP, " \--driftfile "=" \fIstring\fP

   121 The name and path of the frequency file,

   122 /var/ntp/ntp.drift by default.

   123 .TP

   124 .BR \-g ", " \--panicgate

   125 Allow the first adjustment to exceed the panic limit.

   126 .sp

   127 Normally,

   128 \fBntpd\fR

   129 exits with a message to the system log if the offset exceeds the panic threshold, which is 1000s by default. This option allows the time to be set to any value without restriction; however, this can happen only once. If the threshold is exceeded after that,

   130 \fBntpd\fR

   131 will exit with a message to the system log. This option can be used with the

   132 -q

   133 and

   134 -x

   135 options.

   136 See the

   137 tinker

   138 configuration file directive for other options.

   139 .TP

   140 .BR \-k " \fIstring\fP, " \--keyfile "=" \fIstring\fP

   141 Specify the name and path of the symmetric key file.

   142 /etc/inet/ntp.keys

   143 is the default.

   144 .TP

   145 .BR \-l " \fIstring\fP, " \--logfile "=" \fIstring\fP

   146 Specify the name and path of the log file.

   147 The default is the system log file.

   148 .TP

   149 .BR \-L ", " \--novirtualips

   150 Do not listen to virtual IPs. The default is to listen.

   151 .TP

   152 .BR \-m ", " \--mdns

   153 Register as a NTP server with mDNS system. Implies that you are willing to serve time to others.

   154 .TP

   155 .BR \-n ", " \--nofork

   156 Do not fork.

   157 .sp

   158 .TP

   159 .BR \-N ", " \--nice

   160 To the extent permitted by the operating system, run

   161 \fBntpd\fR

   162 at the highest priority.

   163 .TP

   164 .BR \-p " \fIstring\fP, " \--pidfile "=" \fIstring\fP

   165 Specify the name and path of the file used to record

   166 \fBntpd\fR's

   167 process ID.

   168 .TP

   169 .BR \-P " \fInumber\fP, " \--priority "=" \fInumber\fP

   170 To the extent permitted by the operating system, run

   171 \fBntpd\fR

   172 at the specified

   173 sched_setscheduler(SCHED_FIFO)

   174 priority.

   175 .TP

   176 .BR \-q ", " \--quit

   177 Set the time and quit.

   178 \fBntpd\fR

   179 will exit just after the first time the clock is set. This behavior mimics that of the

   180 \fBntpdate\fR

   181 program, which is to be retired.

   182 The

   183 -g

   184 and

   185 -x

   186 options can be used with this option.

   187 Note: The kernel time discipline is disabled with this option.

   188 .TP

   189 .BR \-r " \fIstring\fP, " \--propagationdelay "=" \fIstring\fP

   190 Specify the default propagation delay from the broadcast/multicast server to this client. This is necessary only if the delay cannot be computed automatically by the protocol.

   191 .TP

   192 .BR \-s " \fIstring\fP, " \--statsdir "=" \fIstring\fP

   193 Specify the directory path for files created by the statistics facility. This is the same operation as the statsdir statsdir command.

   194 .TP

   195 .BR \-t " \fInumber\fP, " \--trustedkey "=" \fInumber\fP

   196 Add a key number to the trusted key list. This option can occur more than once. This is the same operation as the trustedkey key command. 

   197 .TP

   198 .BR \-U " \fInumber\fP, " \--updateinterval "=" \fInumber\fP

   199 interval in seconds between scans for new or dropped interfaces.

   200 This option takes an integer number as its argument.

   201 .sp

   202 Give the time in seconds between two scans for new or dropped interfaces.

   203 For systems with routing socket support the scans will be performed shortly after the interface change

   204 has been detected by the system.

   205 Use 0 to disable scanning. 60 seconds is the minimum time between scans.

   206 .TP

   207 .BR \--var "=" \fInvar\fP

   208 make ARG an ntp variable (RW).

   209 This option may appear an unlimited number of times.

   210 .sp

   211 .TP

   212 .BR \--dvar "=" \fIndvar\fP

   213 make ARG an ntp variable (RW|DEF).

   214 This option may appear an unlimited number of times.

   215 .sp

   216 .TP

   217 .BR \-x ", " \--slew

   218 Slew up to 600 seconds.

   219 .sp

   220 Normally, the time is slewed if the offset is less than the step threshold, which is 128 ms by default, and stepped if above the threshold.

   221 This option sets the threshold to 600 s, which is well within the accuracy window to set the clock manually.

   222 Note: Since the slew rate of typical Unix kernels is limited to 0.5 ms/s, each second of adjustment requires an amortization interval of 2000 s.

   223 Thus, an adjustment as much as 600 s will take almost 14 days to complete.

   224 This option can be used with the

   225 -g

   226 and

   227 -q

   228 options.

   229 See the

   230 tinker

   231 configuration file directive for other options.

   232 Note: The kernel time discipline is disabled with this option.

   233 .TP

   234 .BR \-? , " \--help"

   235 Display usage information and exit.

   236 .TP

   237 .BR \-! , " \--more-help"

   238 Extended usage information passed thru pager.

   239 .TP

   240 .BR " \--version"

   241 Output version of program and exit.  

   242 .SH OPTION PRESETS

   243 All of the above options except the last three may be preset

   244 by loading values from environment variables named:

   245 .nf

   246   \fBNTPD_<option-name>\fP or \fBNTPD\fP

   247 .fi

   248 .aj

   249 The environmental presets take precedence (are processed later than)

   250 the configuration files. The option-name should be in all capital letters.

   251 For example, to set the --quit option, you would set the NTPD_QUIT environment

   252 variable.

   253 .SH AUTOMATIC SERVICE MANAGEMENT (SMF)

   254 \fBNTP\fR on Solaris is managed via the service management facility described in 

   255  \fBsmf\fR(5). There are several options controlled by services properties which 

   256 can be set by the system administrator. The available options can be listed by

   257 executing the following command:

   258 .nf

   259 	svccfg -s svc:/network/ntp:default listprop config

   260 .fi

   261 .aj

   262 Each of these properties can be set using this command:

   263 .nf

   264 	svccfg -s  svc:/network/ntp:default setprop \fIpropname\fP = \fIvalue\fP

   265 .fi

   266 .aj

   267 The available options and there meaning are as follows:

   268 .TP

   269 .BR config/always_allow_large_step

   270 A boolean which when false, prevents ntpd from allowing step larger than 17 minutes except once

   271 when the system boots. The default is true, which allows such a large step once each time ntpd starts.

   272 .TP

   273 .BR config/debuglevel

   274 An integer specifying the level of debugging requested. A zero means no debugging. The default is zero.

   275 .TP

   276 .BR config/logfile

   277 A string specifying the location of the file used for log output. The defualt is /var/ntp/ntp.log

   278 .TP

   279 .BR config/no_auth_required

   280 A boolean which when true, specifies that anonymous servers such as broadcast, multicast and active peers 

   281 can be accepted without any pre-configured keys. This is very insecure and should only be used if

   282 the nework is secure and all the systems on it are trusted. The defualt is false.

   283 .TP 

   284 .BR config/slew_always

   285 A boolean which when true, instructs ntpd to slew the clock as much as possible, instead of stepping the clock. It 

   286 does not prevent all stepping, but increases the threshold above which stepping is used. It also disables the use

   287 of the kernel \fBNTP=fP facility, which is incompatible with long slew times. The default is false.

   288 .TP

   289 .BR config/wait_for_sync

   290 A boolean which when true, causes the \fBNTP\fP service to delay coming completely on-line until after the first 

   291 time the system clock is synchronized. This can potetially delay the system start up by a significant amount. The

   292 default is false.

   293 .TP

   294 .BR config/mdnsregister

   295 A boolean which when true, will cause the daemon to register with the network mDNS system. The default is false.

   296 .TP

   297 .BR config/verbose_logging

   298 A boolean which when true, cause the daemon to issue logging messages. The default is false.

   299 .SH NOTES

   300 The system clock must be set to within 68 years of the actual time before \fBntpd\fR is started.

   301 .LP

   302 The \fBntpd\fR service is managed by the service management facility, \fBsmf\fR(5), under the service identifier:

   303 .sp

   304 .in +2

   305 .nf

   306 svc:/network/ntp:default

   307 .fi

   308 .in -2

   309 .LP

   310 Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using \fBsvcadm\fR(1M). The service's status can

   311 be queried using the \fBsvcs\fR(1) command.

   312 .sp

   313 In contexts where a host name is expected, a -4 qualifier preceding the host name forces DNS resolution to the IPv4 namespace, while a -6 qualifier forces DNS resolution to the IPv6 namespace.

   314 .LP

   315 Various internal \fBntpd\fR variables can be displayed and configuration options altered while the \fBntpd\fR is running using the \fBntpq\fR and \fBntpdc\fR utility programs.

   316 .LP

   317 When \fBntpd\fR starts it looks at the value of umask, and if zero \fBntpd\fR will set the umask to 022.

   318 .LP

   319 Source for \fBntpd\fR is available on http://src.opensolaris.org.

   320 .LP

   321 The documentation available at /usr/share/doc/ntp is provided as is from the 

   322 \fBNTP\fR distribution and may contain information that is not applicable to 

   323 the software as provided in this partIcular distribution.

   324 .PP

   325 .SH ATTRIBUTES

   326 See

   327 .BR attributes (5)

   328 for descriptions of the following attributes:

   329 .sp

   330 .TS

   331 tab() box;

   332 cw(2.75i) |cw(2.75i)

   333 lw(2.75i) |lw(2.75i)

   334 .

   335 ATTRIBUTE TYPEATTRIBUTE VALUE

   336 _

   337 AvailabilitySUNWntpu

   338 =

   339 Interface StabilityUncommitted

   340 .TE 

   341 .PP

   342 .SH SEE ALSO

   343 .LP

   344 \fBsvcs\fR(1), \fBsntp\fR(1M), \fBntp-keygen\fR(1M), \fBntpdate\fR(1m), \fBntpq\fR(1M), \fBntptrace\fR(1M), \fBntptime\fR(1M), \fBsvcadm\fR(1M), \fBntpdc\fR(1M), \fBrename\fR(2), \fBattributes\fR(5), \fBsmf\fR(5)

   345