The Network Time Protocol (described in RFC-1305) is used to keep a computer's clock synchronized with a set of time servers distributed over a network, each with varying accuracy and reliability.
This is very useful when you are using machines that share resources that have a timestamp associated with them. If one computer has a different idea of the time from another, strange errors can show up when using the shared resources. A good example is a file server and its clients. The shared resource are the files which almost always have timestamps associated with them.
Many of the latest versions of system software for all platforms include support for NTP servers. Currently CIS maintains three public NTP time servers for on-campus use. They are:
Server Address ntp1.tamu.edu 128.194.254.7 ntp2.tamu.edu 128.194.254.8 ntp3.tamu.edu 128.194.254.9 These are stratum-2 NTP servers which are synchronized against a WWVB radio clock, providing very accurate times. It is recommended that, if possible, the server names be used in configuration files, not the IP addresses. The use of names, in conjunction with DNS, will reduce the chance of loss of service should the addresses of any of the machines change.
For systems which are off campus, you are welcome to use ntppub.tamu.edu. Please send mail to ntp@tamu.edu so that we can keep a record of who is using our service.
For systems which only allow one server to be specified, the name `time.tamu.edu' should be used. This name should only be used in conjunction with DNS. For Unix clients, there is a sample ntp.conf file located here.