GNU/Linux Desktop Survival Guide by Graham Williams
Desktop Survival Project Home Preface Advocacy History Distributions Installation Basic Survival Wajig Audio AbiWord APM Backup Bash Booting Cameras CD Chinese ChRoot Clock Commercial Conference Management Configuration CRON CVS Databases DIA Directories Disks Documentation DVD Email Eye of Gnome Evolution File Systems Firewalls Floppy Disks Fonts Ghemical GIMP Glade Gnome GnuCash Gnumeric GQView Graphics Groups HTML Editors ImageMagick Initialisations on Booting Java KDE Kernels Keyboard Konqueror KVM Switch LaTeX Log System Login Magellan Mathematics Memory Modems Mounting Devices MS/Windows Music MySQL Nautilus Networks NFS NT File System OpenOffice.org Oracle Packages Partitions Passwords PDF Photos PPP Presentations Printing Python R Remote Desktops Rsync Samba Scanning Science Security SH File System Sketch Spell SPlus Spruce SSH SUDO Subversion Swap Themes USB Video Virtualization Web Word X XML Sample Installations Troubleshooting Index

Using NTP

The Network Time Protocol (NTP) daemon provided by the ntp-simple package is by far the easiest way to manage the accuracy of your clock, particularly if you are connected to the internet (even if only intermittently).

The ntp-simple daemon (ntpd) effectively sets the clock by speeding it up or slowing it down depending on its natural drift so that it gets in sync and stays there. This avoids a ``sudden shock'' to the system with a dramatic change to the time, although mostly the system can handle it.

The primary configuration required is to identify an NTP server. Look at the lists at http://www.eecis.udel.edu/~ntp/, for example.

After running ntpd for a little while your clock will be set to an accurate time and will maintain an accurate time. However, if the amount of difference is too great then ntpd will not modify the clock. After setting up ntp-simple you can install ntpdate and on install (and reboot) the clock will be updated to the correct time according to the server you have chosen for ntp-simple.

With ntp-simple installed on one of your hosts, Velox (104.33) for example, on the local network you can now use Velox (104.33) as a ntp server simply by installing ntp on each machine and pointing them to Velox (104.33) as the server.