Per Jessen wrote:
Cristian Rodríguez wrote:
El 15/03/13 09:27, James Knott escribió:
The big one is to reduce the load on the remote server. It's not considered "polite" to have several devices hitting a public server. Well, you dont use just one server, if you use a server pool you might get dozens of servers to query.
I express my skepticism that behaving NTP clients would pose a major load on resources or bandwidth to public NTP servers.
I agree with that - the whole reason the pool concept was set up was to be able to shoulder hundreds of thousands of clients, e.g. SOHO routers. I still think it's nicer to use a local server if one is available.
All I can suggest to you both is RTFM then. http://www.pool.ntp.org/en/use.html ... "If you have a static IP address and a reasonable Internet connection (bandwidth is not so important, but it should be stable and not too highly loaded), please consider donating your server to the server pool." ... "If your Internet provider has a timeserver, or if you know of a good timeserver near you, you should use that and not this list - you'll probably get better time and you'll use fewer network resources." ... "Be friendly. Many servers are provided by volunteers, and almost all time servers are really file or mail or webservers which just happen to also run ntp. So don't use more than four time servers in your configuration, and don't play tricks with burst or minpoll" ... *"If you are synchronising a network to pool.ntp.org, please set up one of your computers as a time server and synchronize the other computers to that one."* -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org