"David L. Mills" <[EMAIL PROTECTED]> writes: > The rate violation is caught in the MRU list, which can be retrieved > using ntpdc and the monlist command. When the number of clients is > small, the list can be retrieved over the net. When the number of > clients is larte, like several hundred, there are many UDP packets and > one or more are usually dropped. The solution at present is to run > ntpdc on the server machine and pipe the monlist output to a local > file. > > Each time a KoD is sent a counter is increased by one. Once each > second the counter is decreased by one. If an offending packet arrives > and the counter is less than 2, a KoD is sent; otherwise, the packet > is dropped without further action. There probably should be some > triage, but not without additional complexity.
This is both interesting and useful, but begs the question, which was what "monitor" semantics are and how the parameter should be specified (0-1, percentage, whatever) Also, it wouldn't hurt to copy-paste what you wrote above into the doc on udel.edu :) DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
