On 9/25/2013 2:05 PM, Ralph Mitchell wrote:
Just FYI, the clock drift is measured by comparing the date/time sent at the bottom of the client message against the Xymon server clock. I have some systems on slow network connections and sometimes it takes a couple of retries for the status report to get through, and by then the client time is often 10 - 30 seconds adrift.
In other words, it's not simply the client working out that its own clock is slow.
I know that Ryan specifically said he didn't want to go the route of an ext script. I mention this here for others who may search the archives for this topic.
I use an ext script which looks at the output of "/usr/sbin/xntpdc -sn" It sends a yellow if the clock has drifted more than a second or is synchronized at a stratum greater than 9. It sends a red if the clock has drifted more than five seconds.
-- Do things because you should, not just because you can.
John Thurston 907-465-8591 John.Thurston at alaska.gov Enterprise Technology Services Department of Administration State of Alaska