Installing SoftBench

Customizing SoftBench CM Configuration
Performing SoftBench CM Administrator Tasks
Appendix C 81
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.