Thanks. I was kind of hoping someone would say "ah just run with the
--howyoudoing option and check the exit code!"

Maybe that would be a nice feature :)

-- 
  James Patterson
  [email protected]

On Thu, Aug 1, 2013, at 05:39 AM, Christoph Lechleitner wrote:
> Am 2013-08-01 09:58, schrieb James Patterson:
> > Hello,
> > 
> > I have two questions.
> > 
> > What's the best way
> > of asking ntpd if it is receiving time from a good time source?
> 
> You remind me that I should start to monitor our timeservers better (2
> of which are in the pool).
> 
> Our main monitoring tool is Icinga (a Nagios fork), and it comes with
> several ntp related plugins.
> 
> check_ntp_peer seems to be apropriate, see attached help text.
> 
> I hope I don't break any list rules by attaching something, sorry
> otherwise.
> 
> Does anybody have experience using check_ntp_peer and can recommend
> apropriate jitter margins for, say level 3 to 5 time servers?
> 
> Thanks,
> 
> Regards,
> 
> Christoph
> 
> _______________________________________________
> pool mailing list
> [email protected]
> http://lists.ntp.org/listinfo/pool
> Email had 1 attachment:
> + check_ntp_peer_--help.txt
>   3k (text/plain)

-- 
http://www.fastmail.fm - Faster than the air-speed velocity of an
                          unladen european swallow

_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool

Reply via email to