HP UX SoftBench Software manual Setting Logging and Debug Options, 346

Customizing SoftBench CM Configuration

Modifying the Configuration Files

If the cm.permission file is missing, or no match is found, no access is allowed. You should specify a default entry such as:

*@15.* -abf-cdilmnptuwx-oqz-esvy /

;

Setting Logging and Debug Options

The cm.option file specifies two archive options:

	LogOptions	The recommended (default) setting for logging is to log
		every modification operation into the
		/var/opt/softbench/cm/activityLog file. The
		option letters are position independent (see Table B-2).
LogOptions:	abf-cdilmnptuwx-oqz-esvy # Logging options (full list)
LogOptions:	cdilmnptuwx-oqz-esvy # Logging options (recommended)
	Debug	Enables writing of debugging information into the file
		/var/opt/softbench/cm/msglog. Debug levels range
		from 1 to 5. Higher numbers result in more output.

Debug: 1

Use the cron utility to trim the log files periodically because the log files have no maximum file length.

Controlling Client Machine Access to the SoftBench CM Server on HP-UX

The inetd.sec file determines the list of client machines that have access to the archive server machine.

•If inetd.sec is missing or does not contain an entry for softcm, all users have access to the archive files, subject to the cm.permission. For more information, see “Defining User Access to the Server” on page 342.

•If inetd.sec exists, but is inaccessible to the softcm user, SoftBench CM denies all access.

•Otherwise, the softcm service entry determines access according to the standard inetd.sec constructs. (See the inetd.sec(4) reference page for more information.)

346 Appendix B