This is an old revision of the document!

Fresh HOWTO in need of proofreading. Enjoy. Niki Kovacs Fri Sep 7 18:53:47 CEST 2012

Looks good content-wise, Niki, but titles and headings need proper capitalization. I can fix if you would like me to. — V. T. Eric Layton 2012/09/07 20:50

Looks OK to me. I've stated my opinion of the capitalisation rule on the styleguide discussion page. — Brian Lawrence 2012/09/08 06:10

There is a HUGE problem in this HOWTO: a sysadmin should NEVER select a time server, but always go through the pooling facility of ntp.org - this prevents individual time servers from being swamped by time sync requests. In other words, one should always use the ISO two-letter country code, for instance: de.pool.ntp.org for Germany, uk.pool.ntp.org for the United Kingdom and so on and so forth. Please see: http://www.pool.ntp.org/en/use.html and correct accordingly…

As per Niki request, I'm mentioning here that I (cmyster) have added the minor change of NTP sync without daemonizing.

Quoting from http://www.pool.ntp.org: “As pool.ntp.org will assign you timeservers from all over the world, time quality will not be ideal. You get a bit better result if you use the continental zones (For example europe, north-america, oceania or asia.pool.ntp.org), and even better time if you use the country zone (like ch.pool.ntp.org in Switzerland) - for all these zones, you can again use the 0, 1 or 2 prefixes, like 0.ch.pool.ntp.org. Note, however, that the country zone might not exist for your country, or might contain only one or two timeservers. If you know timeservers that are really close to you (measured by network distance, with traceroute or ping), time probably will be even better.” Which means the information displayed on the HOWTO is correct. Niki Kovacs

Thanks, Niki, I learned something today! (isn't that what this wiki is all about?)