The Sysadmins Daily Grind: OpenNTPD

Finding Time

Article from Issue 51/2005
Author(s):

On vacation we may be happy just to check the position of the sun,but computers need a more accurate measure of time. Luckily, there are atomic clocks that can receive time signals by radio and off the Internet.

I’m a practical person, and also a big believer in being punctual. Of course, I expect my servers to keep perfect time. Half a minute can make all the difference between a happy admin and a chaotic network. Just as an example, imagine someone sends me an email message. The first thing that happens is that the spam filter gets to check the message, which it then hands over to the anti-virus server. If the AV server is happy with the message, the next step along the way is the mail hub, which locates the correct mail server and forwards the message to that location, where the mail server finally dumps the message in my inbox. In other words, email messages on my network are handled by no less than four servers. If there is a problem, I check the logfiles to see where things are going wrong. And this is where precise timekeeping becomes imperative.

Buy this article as PDF

Express-Checkout as PDF
Price $2.95
(incl. VAT)

Buy Linux Magazine

SINGLE ISSUES
 
SUBSCRIPTIONS
 
TABLET & SMARTPHONE APPS
Get it on Google Play

US / Canada

Get it on Google Play

UK / Australia

Related content

  • Charly's Column: Ntpd

    The Network Time Protocol keeps Charly up to date at all times. To put all of this punctuality in the service of the common good, he even exports the time signal.

  • Admin Workshop: NTP

    Networks often require very accurate timekeeping. The Network Time Protocol provides the time with precision.

  • Charly's Column

    Parallel SSH is the name of an easy-to-configure tool that our resident sys admin, Charly, now routinely deploys whenever he needs to launch the same programs, copy the same files, or kill the same processes simultaneously on multiple computers.

  • Charly's Column

    Despite the cyclical disruptions so typical of LUG meetings, our intrepid columnist, Charly, reveals how he set the system time in spite of a blocked NTP port.

  • Charly's Column

    Some of Charly’s servers run the SSH daemon on port 443 rather than on the standard port 22. If an SSL-capable Apache web server starts causing trouble, his method of settling the dispute is sslh.

comments powered by Disqus

Direct Download

Read full article as PDF:

Charly_Column.pdf (91.49 kB)

News