[ntp:questions] Re: Problem with good synchronization.

David L. Mills mills at udel.edu
Sun Oct 17 10:40:16 UTC 2004


By default, the local clock driver will not become active unless all 
other sources fail. Catch two bulls at the same stratum and run 
symmetric mode between them. The cows follow either bull or both. Now, 
if either bull loses its cowboy, it follows the other. That was my 
intent and I just verified it works. If both cowboys fail, the bulls 
will agree to disagree.


Harlan Stenn wrote:

> Dave,
> I've never seen that behavior (but uyou havemore experience).
> I have tried the mechanism you describe, and in that case I have had the
> primary external timesource disappear and then the bulls head off in their
> own directions, with different cows following different bulls.
> H
> --
> In article <ckq6bo$ad1$1 at dewey.udel.edu>,
> David L. Mills <mills at udel.edu> wrote:
>>The problem I observed was, when three strata bulls and a number of cows 
>>were involved, developed a deadly embrace where the cows saw the stratum 
>>oscillate first to one bull and then another. This caused frequent 
>>timeouts as the cows waited for a stratum lower than theirs to come 
>>back. The bottom line is not to be so adventurous, keep the bulls at one 
>>stratum and let the cows eat equal stratum grass.
>>Harlan Stenn wrote:
>>>Please say more - I have been doing it this way for years.
>>>When "all is well" *everybody* syncs to the main server, and then
>>>everybody except the main server runs at S+1.
>>>If the main server fails folks slowly sniff around and the #2 box soon
>>>becomes the "lead dog".
>>>On rare occasions I see a clique form, but it is usually short-lived and
>>>I have never seen a case where the different cliques have "significantly"
>>>different time.

More information about the questions mailing list