DCE Installation, Configuration, and Management Guide

Recommended Usage
HP NonStop DCE Installation, Configuration, and Management Guide429552-005
6-2
Managing the cdsadv and cdsclerk Processes
8. Issue this cdscp command for each directory listed in Step 7:
create replica /.:/dir_name clearinghouse /.:/sys_ch
9. Enter this cdscp command for each directory:
set dir /.:/dir_name to new epoch master /.:/sys_ch readonly
/.:/old_ch
Managing the cdsadv and cdsclerk Processes
The NonStop DCE cdsclerk processes within a virtual host are started by
dce_config, not by the cdsadv utility. In the OSF implementation, a cdsclerk
process is started for each UNIX user ID. In NonStop DCE, cdsclerk processes are
shared among users.
The number of clerks is configured by the dce_config environment variable
TOTAL_CLERKS. The default value is TOTAL_CLERKS=1. If necessary, the configured
number of cdsclerk processes can be changed without cell reconfiguration:
1. In the configuration database file /opt/dcelocal.hostname/dce_cf.db,
where hostname is the name of the virtual host:
a. Modify the value for TOTAL_CLERKS to the desired number of cdsclerk
processes.
b. Verify that there is a processor assignment entry for each cdsclerk beginning
at cdsc0. For example, if TOTAL_CLERKS is set to 3, add the entries:
cdsc0_cpu 0
cdsc1_cpu 1
cdsc2_cpu 0
2. If the number of cdsclerk processes has been increased, execute the
rc.dce.hostname script or the dce_config start option, which starts the
cdsclerk processes.
Note. Do not change the epochs in the order listed by the command in Step 7. Change
the epochs of all subdirectories before changing the epoch of a directory itself. For
example:
Change the epoch of the directory /.:/a/b/c before that of /.:/a/b
Change the epoch of the directory /.:/a/b before that of /.:/a
And so on
The root directory epoch is the final epoch modified.
Note. All cdsclerk processes are started with the same priority.