OSF DCE Administration Guide--Core Components

Chapter 17. Managing Clerks, Servers, and
Clearinghouses
CDS clerks, servers, and clearinghouses are initially created and started as part of the
CDS clerk and server configuration. Thereafter, clerk and server processes are created
and started with a series of commands that are executed either manually or by the startup
scripts on the systems where they are running. These CDS entities are largely self-
regulating and, apart from routine monitoring, require only minor management
intervention.
This chapter explains how to monitor CDS clerks, servers, and clearinghouses and
perform other management tasks, such as backing up namespace information.
17.1 Monitoring Clerk, Server, and Clearinghouse Counters
Every clerk, server, and clearinghouse maintains a set of attributes called counters to
keep track of the read, write, and other operations that it performed, or that were
performed on it, since it was last started up. You can monitor these counters to determine
the type and volume of the CDS traffic that is being generated on your network.
Clerk, server, and clearinghouse counters are fully described in the OSF DCE
Administration Reference.
17.1.1 Displaying Clerk Counters
Use the CDS control program (cdscp) show clerk command to display the current
counter values for a clerk. For example, to display the current values of all attributes that
are associated with a clerk, you enter the following command:
cdscp> show clerk
124243 Tandem Computers Incorporated 17−1