| NTP uses as its logfile /var/adm/syslog/syslog.log . If you want to turn on monitoring traffic counts, you can do so by either using the xntpdc command monlist or adding the line enable monitor . It is a common feature that is activated by interested NTP administrators. In this way, we can monitor where requests are coming from and if necessary restrict access based on subnet address, IP address, or even relationship with another node. I will leave you to explore these on your own. Something else that you may come across is the concept of slewing time. The configurations I have suggested here include a step-change at system boot-up with the ntpdate command. Therein, xntpd makes the necessary small adjustments as necessary. These small adjustments will, we hope, not be noticed by most applications. If, however, you have a particularly sensitive application, you can enforce xntpd to make all adjustments in a very slow fashion. This is known as slewing . When we have particularly slow WAN links, the offset encountered may be such that significant step-change will be necessary, sometimes even backward. This can cause problems to databases, particularly financial applications. If this sounds like it may apply to you, investigate the “x option to xntpd (if used, ensure that you update the line export XNTPD_ARGS= in the file /etc/rc.config.d/netdaemons ). This will force xntpd to slew times gently toward a zero offset. This means that your clocks will take significantly longer to synchronize with your timeservers. A similar behavior can be found with ntpdate and the “B option. I leave it to you to think about it. |
