Statistics files are useful to view local clock synchronization performance. As a minimum a configuration file needs to specify a server that should be used for synchronization along with a drift file to store local clock frequency.
However, a more complete configuration file will include multiple servers, drift file and a statics directory:. The command provides a list of configured peers and their associated synchronization performance characteristics.
The first character in the peer list is a tally code that indicates the status of synchronization. This indicates that the local system clock is synchronized to the peer. The peer may be used in the event of the system peer being discarded. Other characters generally indicate that the clock has been discarded by the selection algorithm.
Refid — indicates the synchronization source of the peer. However, it may also be an address if the peer is a lower stratum in the NTP hierarchy. Stratum 1 is the highest level, 15 the lowest.
Type — the peer type — local, unicast, multicast or broadcast. Most peers are accessed in unicast mode. Offset — the current offset, or time difference, between the peer and local system time. Jitter — a measurement of variance of timing packets from the peer in milliseconds. This is an indication of clock quality. Lower jitter indicates higher quality clock.
It allows a client to authenticate a server for trusted information exchange. Authentication is based on a number of agreed keys, or passwords, that are available to both client and server. When a message is transferred from server to client, it is appended with an encrypted version of one of the keys. Hosts on the local network are not permitted because of the "restrict default" line above. To change this, for example to allow hosts from the By default, as of Red Hat Enterprise 6.
By default, the ntp. These are largely self explanatory. See the explanation of the specific commands Section Unfortunately at least the ntp. Current versions of ntpd generate only a very limited set of log messages by default during operation. At least in case of debugging it should be helpful to receive more detailed information.
The line. Even though the ntpq command can be used to check ntpd 's current state and time synchronization performance, it is often very helpful to let ntpd generate some statistics files. For example the loopstats file shows how the estimated system time offset and drift compensation develop over time. With a weekly file you can easily see how the clock drift varies cyclically over days, which is due to cyclic variations of the ambient temperature, and how these changes affect the time offset.
Similarly, additional filegen lines can be added for peerstats, clockstats, and rawstats. Please note older versions of ntpd may not support all of these additional statistics file types.
If ntpd sometimes runs in a chroot jail and sometimes doesn't, e.
0コメント