ADMIN - Explore the new world of system administration! Special introductory offer! Order by September 30th to save 10% off the regular subscription price! Each issue delivers technical solutions to the real-world problems you face every day. Learn the latest techniques for better:
network security
system management
troubleshooting
performance tuning
virtualization
cloud computing
on Windows, Linux, Solaris, and popular varieties of Unix.
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.
I am writing this article from the LUG Camp at Wuppertal Germany, and the time is… – er, I have no idea. A kind person from the LUG Flensburg hands me a bottle of Flensburg beer, and I say “Thanks”… Enough has already been said about NTP (Network Time Protocol) based time synchronization, and in fact, I confess to having written about NTP in the past. But today, I will discuss how to time sync without NTP. Up curtain and welcome to HTPDate [1] Of course, NTP is the tool of choice if you need to sync the system clock across a network. But there are times when network synchronization is not possible. For example, if the machine you need to sync is hiding behind a totally hardened firewall maintained by a totally hardened admin who says things like “NTP? Never heard of it, so it must be something bad!”
Get 3 Issues + 3 DVDs for the price of a single issue!
Let Linux Magazine's hands-on, technical articles guide you in your daily Linux use. Check out bonus DVDs like Ubuntu, SUSE, or Fedora and save the download.
Only available for a limited time. Don't miss out!
Comments