HP-UX Internet Services Administrator's Guide (May 2010)

Verifying That xntpd is Running
Issue the following command to determine out if xntpd is running:
/usr/bin/ps -ef /usr/bin/grep xntpd
This command reports the process identification (PID), current time, and the command
invoked (xntpd). Following is an example output:
daemon 4484 1 0 Feb 18 ? 0:00 xntpd
Ensure that syslogd is configured to log daemon information messages to the file
/var/adm/syslog/syslog.log. To check this configuration, ensure that the file
/etc/syslog.conf includes one of the following entries:
*.info /var/adm/syslog/syslog.log
or
daemon.info /var/adm/syslog/syslog.log
If xntpd is not running, check the syslog file for related messages.
NTP Associations
Each NTP daemon must form an association with a time source: a higher-level (lower
stratum) server for stratum-1 servers, or an external clock. NTP daemons can form
additional associations with peer servers. Use the following command to list the NTP
associations established by the local NTP daemon:
/usr/sbin/ntpq -p
In the output, an asterisk (*) must appear next to the node name to indicate that an
association has been formed.
Table 4-8 indicates that the local NTP daemon has established an association with the
NTP daemon on node good.cup.hp.
Table 4-8 An ntpq Output Indicating NTP Associations
dispoffsetdelayreachpollwhenstrefidremote
====================================================================
16.40-0.165.4337764292LOCAL(1)*good.cup.hp
06431-0.0.0.0bad
If the local node is unable to form an association with its higher-level server or its peer,
you must login to the higher-level server or peer and issue the following command:
/usr/sbin/ntpq -p
Verify whether the higher-level server or peer has established an association with a
time source.
Troubleshooting NTP 71