Miroslav Lichvar <mlich...@redhat.com> writes: > I think you do. To prevent the source from being rejected as a > falseticker it needs to have a larger root distance. That could be from > a larger dispersion or delay. You modified the refclock jitter, which > ends up in the peer dispersion (after some weighting). Another approach > would be to specify a minimum for the peer dispersion directly. There > could be also an option to specify a minimum delay. But adjusting it in > the refclock specific code, as you did, makes perfect sense to me.
Which of the alternatives do you prefer? I got one way working, but I am willing to test any other in case you have a patch or could at least tell me where to enforce the minimum in the code to create a patch. In the end, it would be great to get the needed functionality into ntpd. Michael _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
