DTS Server Programs

· The dtsd daemon, which is also installed on a DCE client machine, is configured to run as a server when installed on a DTS server machine. As a server process, dtsd synchronizes with other DTS servers, in addition to synchronizing the local clock, as it does on a client machine.

· The dts_device_name_provider specifies the communications between the DTS server process and the time-provider process. For device_name, substitute the device you are using, which can be a radio, clock, or modem, or another source of UTC time for DTS. A time provider is optional. If you use a time provider, it must connect to a server process.

Consider the following guidelines when planning your DTS implementation:

· Each cell needs to have at least three DTS servers. At least three DTS servers are needed in order to detect if one of them is faulty when they are queried for the time. It is preferable to have four or more DTS servers to provide redundancy. The additional servers increase the accuracy of time synchronization. However, increasing the number of servers queried for the time also increases the activity on the network. The administrator must balance the level of accuracy with the amount of network activity.

· A time provider is optional in DTS; however, cells that must be closely synchronized with a time standard need to have at least one time provider.

· Servers need to be located at the sites with the greatest number of different network connections.

There are many network configuration decisions that affect DTS planning. In the OSF DCE Administration Guide - Core Components, you can find details about the total DTS planning process, including configuration planning for Local Area Networks (LANs), extended LANs, and Wide Area Networks (WANs). The OSF DCE Administration Guide - Core Components also explains the criteria you need to use when selecting a time source for your network to use.