C and C++ SoftBench User's Guide

Customizing SoftBench CM Configuration
Performing SoftBench CM Administrator Tasks
Appendix B350
exceed the size of the disk. Several options exist for moving archive
locations:
To move an entire archive hierarchy to another disk:
1. Stop the cmserver process.
2. Copy or move the hierarchy.
3. Modify the cm.mapping file to reflect the new physical location.
To move a portion of an archive hierarchy (subhierarchy) to another disk:
1. Stop the cmserver process.
2. Copy or move the hierarchy.
3. Modify the cm.mapping file to reflect the new physical location.
4. Add a symbolic link or leave an empty directory in the location from
which you moved each subhierarchy.
This lets you browse the parent directory to view the moved
subhierarchy.
To move an archive hierarchy to another machine:
1. Stop the cmserver process.
2. Copy or move the hierarchy.
3. Modify the cm.mapping file to reflect the new physical location.
4. Copy lock information for the portion of the archive hierarchy that
you are moving (see “Modifying the Lockinfo File” on page 349).
5. Add a symbolic link or leave an empty directory in the location from
which you moved each subhierarchy.
6. Have each user replace or update the usehost line in their mapping
file to reflect the move.
If the global fmrc file /opt/softbench/config/fmrc is used, then
the system administrator can edit its usehost entries for all users.
This is usually most practical for sites mounting SoftBench CM from
a central server.
All changes should be made such that the logical paths to files are not
modified. This way, users are less affected by the move and locks are
preserved. Changing the logical hierarchy during a move can cause loss
of lock information.