On Sat, 02 Sep 2006 16:30:10 +0200, Rob Janssen <[EMAIL PROTECTED]>
wrote:

>> However, if I remove 'limited' from the restrict line it seems to
>> work:
>>   
>The rate limiting in ntpd is not usable.

I understand the fact that it's far from perfect ;-)
In general is does give me a overal reduction in spurious traffic,
which is still useful since both my uplink an downlink traffic is
metered.

In actual fact, last week was one of the few times when I was able to
get rid of one abusive client by a combination of 'limited' and 'kod'
- they were taking about 6 times my total average ntp traffic...
though I agree it's not often that this would work.  In that
instances, it wasn't the used of rate limiting that triggered the very
high polling rate, but apparently rebooting my router did it.

Anyway, I suppose my point wasn't to say that 'limited' is the best
thing since sliced bread, just that the monitoring system should not
penalise my score if I do see fit to use it.  I don't think either of
these  ntp.conf entries are unreasonable for a pool server:
| discard average 5 minimum 2
or
| discard average 9 minimum 2

Cheers

Geoff
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers

Reply via email to