[ntp:questions] Let ntp server not synchronize time from other servers

Maarten Wiltink maarten at kittensandcats.net
Thu Aug 28 14:10:09 UTC 2008


"WANG Cong" <xiyou.wangcong at gmail.com> wrote in message
news:cd532c88-96c6-42c2-91fe-cce8a72b4487 at b1g2000hsg.googlegroups.com...
> On Aug 28, 12:49 pm, "Maarten Wiltink" <maar... at kittensandcats.net>
> wrote:

>> server 127.127.1.0
>> fudge 127.127.1.0 stratum 14
>
> Cool! It works! 8-)
> But there's a little problem, when I changed my ntp.conf, I have to
> wait for several minutes until it works well, if not, I got:
>
> 192.168.90.41: Server dropped: strata too high

NTP really solves a different problem than yours. It's slower than
it might be as a result. Nothing you can fix. Live with it.


> I googled a bit, and someone said this is due to the time of the
> server is far from correct, but it is not. See below:
>
> # /usr/sbin/ntpdate -u pool.ntp.org
> 28 Aug 14:23:38 ntpdate[18923]: adjust time server 194.117.9.136
> offset -0.174164 sec
> # LC_ALL=en_US-UTF8 date
> Thu Aug 28 14:23:42 WEST 2008
>
> At the same time, I ran this on the server:
> > date
> Thu Aug 28 14:23:47 BST 2008

That's not the same time. There's a five second difference! Please
realise that you are dealing with a product, and a crowd, to whom
128ms time difference is enough to go to emergency measures, and
500PPM speed difference is enough to stop trying permanently.


[...]
>> Is there any particular reason why you won't take the time from anyone?
>
> Yes, because we want:
>
> 1. Configure the time of the server manually, no matter how wrong it
> is. :)

I've been in that boat. It can be a right pain to test expiration dates
with a clock that won't stay in 2099 or more than a few seconds.

Groetjes,
Maarten Wiltink





More information about the questions mailing list