Quote: (kruepke@berbee.com)Steve,
That is not what the probe is designed to do. If you look at the release note, you will see that its purpose is to monitor NTP servers,
(thanks I did look at the release notes, I didn't word my thread brilliantly)Otherwise, you probably have to script it. It would probably be fairly easy to check the output of the
ntpq command on Linux. I am not sure how you would do it on Windows though. (that's my next challenge cygwin maybe?)
-Keith
FYI
Here's a customize Linux script not all my own work I hasten to add
#!/bin/bash
# time-offset_check.sh
#
# Checks computer clock against specified NTP server. Issues a warning
# on stdout, if the time difference exceeds limit. Requires ntpdate, bc
# and egrep in path. Run from cron as often as you like.
### Options
TIMEZONE=`date | awk '{ print$5 }'`
NTPSERVER='10.17.0.80' # i.e. random server from pool.ntp.org
LIMIT='150.000000' # i.e. 1.000000 (= 1 second)
LOCALTIMEZONE='GMT'
### Do not edit
OFFSET=`/usr/sbin/ntpdate -q $NTPSERVER \
| egrep -o -m 1 -e "offset ((-)?+\.+)" \
| egrep -o -e "+\.+"`
RESULT=`echo "$OFFSET >= $LIMIT" | bc`
if ]; then
echo "`date "+%b %d %H:%M:%S"` `hostname` Warning: Local clock offset ($OFFSET) larger than limit ($LIMIT) - Check NTPD" >> /var/log/messages
fi
if ]; then
echo "`date "+%b %d %H:%M:%S"` `hostname` Warning: Local Time Zone is not set to GMT - Check /etc/sysconfig/clock or /etc/localtime" >> /var/log/messages
fi
exit 0
Thanks for clarifying the ntp_response probe