[70659] in North American Network Operators' Group
Re: ntp config tech note
daemon@ATHENA.MIT.EDU (Adrian Chadd)
Thu May 20 23:48:48 2004
Date: Fri, 21 May 2004 11:48:01 +0800
From: Adrian Chadd <adrian@creative.net.au>
To: "C. Jon Larsen" <jlarsen@richweb.com>
Cc: Adrian Chadd <adrian@creative.net.au>, nanog@nanog.org
In-Reply-To: <Pine.LNX.4.44.0405202324070.20245-100000@pologrounds.richweb.com>
Errors-To: owner-nanog-outgoing@merit.edu
On Thu, May 20, 2004, C. Jon Larsen wrote:
> I checked and the cron job usually adjusts the clock by about 0.2 to 0.3
> sec every hour. Sure thats probably more than ntpd would adjust it in any
> one iteration were ntpd running ...
>
> according to:
> http://www.eecis.udel.edu/~mills/ntp/html/ntpdate.html
>
> its not too kooky or dangerous to use ntpdate + cron rather than ntpd;
> 0.5 sec is given as a cutoff for it being less disruptive when making
> clock adjustments.
>
> Its interesting to hear what other folks are doing. I had assumed folks
> normally don't run ntpd on each and every server and that ntpdate + cron
> was much preferred; maybe I am off-base.
ntpdate can set my clock backwards. ntpd, after you've first run it, won't.
If you're using this to combine logs between machines you may not
appreciate an hourly backwards step in time. :)
adrian
--
Adrian Chadd I'm only a fanboy if
<adrian@creative.net.au> I emailed Wesley Crusher.
