[ntp:questions] Re: NTP, no external time source, peering "Undisciplined Local Clocks" ?

Marc Brett marc at fordson.demon.co.uk
Wed Oct 19 12:11:48 UTC 2005


On Wed, 19 Oct 2005 03:52:56 -0700, "David Schwartz" <davids at webmaster.com>
wrote:

>
>"Marco Molteni" <mmolteni at cisco.com> wrote in message 
>news:200510181619.11961.mmolteni at cisco.com...
>
>> I know I can tell NTP to use the local clock as a time reference, what
>> is called an "Undisciplined Local Clock" in the NTP documentation.
>>
>> Say I don't know if a clock is better than the other, so by configuring
>> B and C to use A as server I risk to have a not so good time if A is
>> unreliable.
>>
>> Can I configure A,B,C to peer with each other in a meshed fashion, so
>> to have each clock influenced by all the others? From what I read I
>> should use the following configuration file on each host:
>>
>> ========== /etc/ntp.conf ======
>> server 127.127.1.0
>> peer hostA
>> peer hostB
>> peer hostC
>> ==================
>>
>> would it work? Is it the best way to obtain the "best" time assuming
>> I don't know if a clock is better than another?
>
>    IMO, NTP is not appropriate for this type of configuration.

But the timed(8) time server daemon might be just what you want.  It'll slow
some clocks and speed up others to keep the whole flock in synch.




More information about the questions mailing list