On Sun, Jun 24, 2012 at 9:18 AM, Thomas Rieschl <[email protected]> wrote: > I looked up the default configuration in Debian. squeeze, wheezy and even > sid uses the exact same configuration as Ted mentioned. No sign of limited. > Seems like this is a new feature?
No, it's been like this as long as limited and kod restrictions have been available. I suspect the creator of the kod-without-limited "restrict default" line that's made its way into so many Linux distributions tried "kod limited", found it crippled ntpdate clients (which exceeded the default rate limits until ntpdate was tamed in 4.2.7p22), and so removed "limited", saw ntpdate clients were happy again, and assumed incorrectly that kod was still active. > Another question: Should I use "iburst" in my "server" directive or not? > There was a thread about 2 years ago about adding iburst to the default > configuration of some distributions. > But it seems that iburst doesn't make much of a difference if my server runs > like forever without a restart, right? I have no objection to iburst being in default configurations. burst would be inappropriate, OTOH. iburst affects initial startup, plus re-acquisition if a server was unreachable. > What about using the "leapfile" setting? Do you recommend that? Yes, particularly for stratum 1 servers (those with working refclocks). If you're getting your time from upstream NTP servers, you can gamble on them getting the leap indication right (check in the last 24 hours of the month UTC), or you can be sure your server will advertise the leap insertion to clients and apply it locally by configuring a correct leapfile. Cheers, Dave Hart _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
