What the? 2017-06-19 23:28 GMT+02:00 Dan Geist <[email protected]>:
> > I support an ecosystem of (a really big number of) clients that are all > intentionally rebooted every night at the same local time. There is indeed > a huge flood of time checks immediately following them since there is no > battery-backed "CMOS-type" clock function on the device (thank you > bean-counters). This is actually kind of nice since it's a really accurate > approximation of worst case scenario. > Back in the days, when i learned my internet basics, i learned to mitigate any unnecessary internet traffic by having _*local proxy servers*_ for each and every possible service. Are you really telling me, you guys are "just going the easy way", leaving all these devices on their defaults instead of setting up your damn very own ntpd acting at least as a stratum 3 proxy for your fscking LAN??? REALLY? Well, i suppose, people who just put a full quote in their answer seem to don't know it better? Sorry if i sound rude or broke any rule over here but i thought, mitigating the problem of producing traffic which is really bogus at this point, was already common sense......... Let's not forget, the ntp pool is there to provide _large customers_ - as in ISPs and hardware vendors - with a _large base of devices_ with a convenient way to provide easy ntp data. It's not invented to make admins just lazy by 'just using the pool' .. or are i am wrong on that? It seems not because even in http://www.pool.ntp.org/en/vendors.html it's stated that: *"Typically the best solution is for your organization to setup your own cluster of NTP servers, for example ntp1.example.com <http://ntp1.example.com>, ntp2.example.com <http://ntp2.example.com> and ntp3.example.com <http://ntp3.example.com> and use those as the default in your configuration."* (and even microsoft does that....) Just my 2 cents, hacky _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
