Performing SoftBench CM Administrator Tasks

SoftBench CM requires a few maintenance tasks to ensure a smooth-running configuration management environment.

Migrating Archive Files From RCS

You can import individual RCS files into SoftBench CM using the -ARCS option of fci. SoftBench CM can also assume management of an existing hierarchy of RCS files.

To migrate archive files from RCS:

Edit the /opt/softbench/config/cm.mapping or /etc/softbench/config/cm.mapping file so that the desired logical path is mapped to the existing directory hierarchy of RCS files.
Make certain that all RCS locks in the hierarchy are removed.
Change the owner (and group) of all files and directories in the hierarchy to "softcm".

Migrating Archive Files From SCCS

To migrate files from existing SCCS archives to SoftBench CM archives:

Create the new SoftBench CM archive hierarchy using the "futil -M" command.
Use the utility "sccstorcs" to convert the SCCS files to GNU RCS format.
Run sccstorcs without any arguments to create the KeyWordEdit script. This script lets you decide which SCCS keywords convert to RCS keyword equivalents. Most users use the default keywords in this script.
Run "sccstorcs s.file" to convert files in the current directory.
Run "find directory -type f -name 's.*' -print | xargs sccstorcs" to convert files in a directory hierarchy. (See the sccstorcs(1) man page for more information on sccstorcs)
Run "fci -ARCS file,v" to create the initial SoftBench CM archive files.
Begin using SoftBench CM for file versioning.

This conversion process preserves the history and contents from the SCCS files.

Modifying the Lockinfo File

The file /var/opt/softbench/cm/lockinfo holds all archive file lock information and is created and maintained automatically. The SoftBench CM server accesses this file for all lock or unlock information requests. It is recommend that you DO NOT modify this file. If you must modify it, follow these steps:

Shut down the SoftBench CM server.
Failing to shutdown the server could cause data corruption and loss of information.
Modify the lockinfo file.

Run the fixinfo program on the lockinfo file:

cd /var/opt/softbench/cm
/opt/softbench/sbin/fixinfo lockinfo outOK outBAD

If "bad = 0" prints, copy the outOK file onto lockinfo:
cp outOK lockinfo
If there are bad records, edit the outBAD file to try to fix the problems.
Run fixinfo on the fixed file.
Concatenate all the "OK" files together and recheck before restarting the SoftBench CM server process.

Creating Archive Backups

SoftBench CM requires no special setup or precautions to backup the SoftBench CM archive files, configuration files, or log files. Follow the normal backup procedures for your SoftBench CM server.

Moving Archive Storage Locations

As a project grows and you add more files to an archive, the archive may exceed the size of the disk. Several options exist for moving archive locations:

To move an entire archive hierarchy to another disk:

Stop the cmserver process.
Copy or move the hierarchy.
Modify the cm.mapping file to reflect the new physical location.

To move a portion of an archive hierarchy (subhierarchy) to another disk:

Stop the cmserver process.
Copy or move the hierarchy.
Modify the cm.mapping file to reflect the new physical location.
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:

Stop the cmserver process.
Copy or move the hierarchy.
Modify the cm.mapping file to reflect the new physical location.
Copy lock information for the portion of the archive hierarchy that you are moving (see “Modifying the Lockinfo File ”).
Add a symbolic link or leave an empty directory in the location from which you moved each subhierarchy.
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.

Troubleshooting

SoftBench CM uses archive log files for quick resolution of problems you may encounter.

Using the Archive Status and Error Log

The SoftBench CM server daemon keeps the file /var/opt/softbench/cm/msglog open in append mode for writing various status and error messages. Look at this file when unexpected events occur.

Log files can grow without bounds if left unchecked. Use an automated process, such as a cron job, to truncate the log files.

Each message in the log files begins with a date stamp. The most common messages include the "Started" and "Terminated" status messages, the configuration file reading messages, and the "Access denied" messages. Some RCS error messages might also show up in the file. These messages are more detailed than the command error messages, so consult the server's msglog file if the command error message is not clear.

Using the Archive Activity Log

The /var/opt/softbench/cm/activityLog file tracks modifications made to archive files. The SoftBench CM server writes a line for every activity that has been selected for logging in the cm.option file. The activityLog file can be moved, truncated, or deleted without affecting SoftBench CM. If deleted, the system recreates the file automatically at runtime.