Per Hedeland wrote:
since ntpdate can't really tell you anything about how
your local ntpd is doing (it seems to use ntpq too, but not for the
offset).
ntpdate -q localhost
would do that (and might be used, when Nagios monitors localhost).
No it wouldn't - it's just plain bizarre: ntpdate can only tell you the
time offset between the queried host and the local host, which will
obviously always be effectively zero with such a query.
Thanks for your clarification; of course you're completely right, I haven't
thought about the semantics of ntpdate.
I'll open a bug ticket for this at the Nagios project, as ntpd monitoring is
obviously seriously botched.
Joachim
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod Email: [EMAIL PROTECTED]
Roedermark, Germany
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.isc.org/mailman/listinfo/questions
