On Jun 11, 2012, at 2:42 PM, Ask Bjørn Hansen wrote: > On Jun 11, 2012, at 14:27, Chuck Swiger wrote: >> It wouldn't have any real effect upon the majority of sites. Anybody >> sync'ed to NTP for >> some time already has the intrinsic offset saved to a drift file, which >> ought to keep even >> freewheeling boxes reasonably well sync'ed for weeks. > > Some large number of systems (appliances, poorly configured general purpose > systems? who knows) use SNTP[1]; they'd immediately stop getting the correct > time. Hopefully if they really really need the correct time, they'd have > been configured to use privately run and managed servers.
You make a decent point, although my takeaway is that one probably should use NTP instead of SNTP whenever possible. For embedded devices like WiFi routers and the like using SNTP which can't easily be changed to run ntpd, they might well be happier pointing to a local NTP server on the same subnet, instead of remote timeservers... YMMV :-) Regards, -- -Chuck _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
