HP-UX Internet Services Administrator's Guide (August 2003)
Configuring NTP
Advanced NTP Topics
Chapter 480
• prefer
This option specifies that the host must be the primary source for
synchronization when it is one of several valid sources. This option is
useful for a time server on a high-speed LAN that is equipped with
an external time source, such as a radio clock. You can use external
sources for time synchronization. However, the local time server
must be the preferred synchronization source.
Apart from these options, you can define the broadcast client in the
configuration file using the broadcastclient yes|no statement. The
statement broadcastclient yes indicates that the local host must listen
for and attempt to synchronize with the broadcasted NTP packets. The
optional statement broadcastdelay
seconds
specifies the default round
trip delay for a broadcaster.
NOTE Every node in an NTP hierarchy must have either a server statement or
a broadcastclient yes statement in its configuration file. Every node
must have an upper-level server. A stratum-1 server must also have a
server statement in its configuration file, which specifies a radio clock or
internal system clock as a time source.
If the local host assumes the role of a server in providing time to the
clients, you need not configure the local host as a time server on the local
system. Instead, you must specify the local host name or IP address in
the server statement in the client system’s configuration file.
If authentication is enabled on the local host, the roles you configure are
subject to the authentication process. For example, if you configure the
local host as a peer or a client of a stratum-1 server, and the remote
server does not satisfy the standards for an authenticated
synchronization source, the local host does not use the remote server as a
time source. See “Configuring Authentication” on page 83 for more
information.
NOTE xntpd is an HP implementation of version 3.2 of a publicly-available
NTP daemon. HP does not guarantee that xntpd is fully compatible with
version 1 or version 2 implementations of the daemon.