OSF DCE Administration Guide--Core Components

Managing the DCE DST
dcecp> dts show
{checkinterval +0-01:30:00.000I-----}
{epoch 0}
{tolerance +0-00:10:00.000I-----}
{tdf -0-05:00:00.000I-----}
{maxinaccuracy +0-00:00:00.100I-----}
{minservers 3}
{queryattempts 3}
{localtimeout +0-00:00:05.000I-----}
{globaltimeout +0-00:00:15.000I-----}
{syncinterval +0-00:02:00.000I-----}
{type server}
{courierrole backup}
{actcourierrole courier}
{clockadjrate 10000000 nsec/sec}
{maxdriftrate 1000000 nsec/sec}
{clockresolution 10000000 nsec}
{version V1.0.1}
{timerep V1.0.0}
{provider no}
{autotdfchange no}
{nexttdfchange 1994-10-30-06:00:00.000+00:00I0.000}
{serverprincipal hosts/gumby/self}
{serverentry hosts/gumby/dts-entity}
{servergroup subsys/dce/dts-servers}
{status enabled}
{uuid 000013ed-000b-0000-b8ef-03a4fcdf00a4}
The example display shows the attribute values for the single server located on the local
node. The attributes that the dts show command displays for a clerk are different. Also,
there will be more attributes displayed for a server (see Tables 25-2 and 25-3).
If you wish to modify the attributes for a DTS clerk or server, you can use the dcecp dts
modify command. Several examples of this command appear in the following
subsections, which describe the settable attributes for clerks and servers. These
subsections also offer suggestions for various attribute settings, depending on your
network configuration.
25.5.1 The minservers Attribute
The minservers attribute specifies how many servers must supply time values to the
system before DTS can synchronize the local clock.
The default and minimum recommended value for the minservers attribute is 3; your
system requires values from three servers in order to compute a reliable new time.
Depending on whether it is a server or clerk, the system has different requirements of the
other systems in the network:
124243 Tandem Computers Incorporated 25−9