On 2008-08-26, Darryl Miles <[EMAIL PROTECTED]> wrote: > Unruh wrote: > > > A far better idea is to monitor the offset from the ntp servers to > > let you know if there is a clock problem. > > I'd appreciate a tool for that. "/usr/sbin/ntpdc -check > 0.0000:0000:0000 -print"
ntpq is the preferred monitoring tool. ntpq -c"rv 0 offset" will tell you the current offset of your ntpd. > that takes various parameters for your acceptable accuracy and returns > with zero/non-zero exit status. That might also dump data like > adjtimex -print and indicate items of concern to the administrator. Collecting information from all those sources is the job for a script. -- Steve Kostecke <[EMAIL PROTECTED]> NTP Public Services Project - http://support.ntp.org/ _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
