Op 24/02/2012 om 12:32:51 +0100, schreef Miroslav Lichvar: > On Fri, Feb 24, 2012 at 12:12:10PM +0100, Leo Baltus wrote: > > Op 24/02/2012 om 11:43:01 +0100, schreef Miroslav Lichvar: > > > I think that will create a positive feedback loop and will not work > > > well, if at all. The instance which sets the clock needs to compare > > > its clock against a stable clock, not something which includes its > > > own clock. > > > > Wouldn't the one running on its own clock mark it as 'bad' in > > comparison with the others? > > I don't think so, how would it know it's bad? > > Even if it would ignore it, the loop would be just longer, it would go > through the other servers. > > > > > In the mean time I have prepared a patch to see if i can get this > > > > working. Any thoughts about testing scenarios? > > > > > > I'm interested to see what the patch does. > > I think this can work only if the server knows what changes to the > local clock the client did so it can fix its sourcestats. >
Ah, I see. Time to go back to the drawing board... -- Leo Baltus, internetbeheerder /\ NPO ICT Internet Services /NPO/\ Sumatralaan 45, 1217 GP Hilversum, Filmcentrum, west \ /\/ beh...@omroep.nl, 035-6773555 \/ -- To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
