Creating a New Clerk or Server
To create a new clerk or server on the node, use the functions of the dce_config script that configure additional DTS clerks and servers (see OSF DCE Administration Guide - Introduction ). The dce_config functions for configuring additional clerks and servers restart the DCE daemon (dtsd) as either a clerk or server.
Just as during initial DTS configuration, if you are creating a server, you must tell the dce_config script the type of server that it is to create: global or local. Before you choose the server type, you should consider the role that the server will play in propagating the network time.
Local servers can have a noncourier role (the value of the courierrole attribute is set to noncourier). A noncourier server does not participate in time propagation. Local servers can also have a courier role (the value of the courierrole attribute is set to courier) or a backup courier role (the value of the courierrole attribute is set to backup). Courier servers have primary responsibility for synchronizing the clocks between the nodes in a segment of the network. Backup couriers are secondary links, which propagate the time when no courier server is available. When you create a local server, the courier role is automatically set to backup.
Global servers must play the noncourier role. They cannot be designated as couriers or backup couriers.
Designating Global and Courier Servers provides more information about server courier roles and instructions for changing the courier role after you create a server.