[ntp:questions] Why does ntp keep changing my conf file?
dhavey at yahoo.com
Wed Sep 22 20:18:50 UTC 2010
The bloody thing made it worse! Look at the graph. It was doing just fine at 0.002147 second offset, then I started ntpd and look what it does. This is definitely not very good for a testbed.
The evil script actually did a better job.
--- On Tue, 9/21/10, David Woolley <david at ex.djwhome.demon.invalid> wrote:
> From: David Woolley <david at ex.djwhome.demon.invalid>
> Subject: Re: [ntp:questions] Why does ntp keep changing my conf file?
> To: questions at lists.ntp.org
> Date: Tuesday, September 21, 2010, 11:16 PM
> Richard B. Gilbert wrote:
> > It not only LOOKS too good to be true, it IS to good
> to be true!
Fixed that ;^)
> > NTPD has not yet been able to contact either
> cogsworth.aero or dns.aero.org.
> Pay attention at the back. This has already been
> > Also, you appear to have forced the poll interval to
> 1024 seconds. 1024 is really great when your clock is
> within a few microseconds of the
> I have a feeling that ntpd does this if there is an
> extended outage.
> > Finally, two servers are not sufficient to allow NTPD
> to do its best.
> It has already been made clear that the requirement here is
> close lock to a single local server which has to be working
> for the system to be valid at all. This is not trying
> to obtain accurate true time from unreliable secondary
> He's been given bad advice about nptdate, but you still
> have to read the actual situation and respond accordingly.
> questions mailing list
> questions at lists.ntp.org
More information about the questions