Modifying the Configuration Files

Configuring Where Archive Files are Stored

The cm.mapping file determines where archive files are physically stored on the server. This file is created during installation and contains default entries that MUST be modified to map to your archive file structure. Together this file and the mapping file determine the relationship between local files and directories and the logical and physical location of archive files and directories (see Figure C-1 “File Mapping Between Local and Archive Files ”).

Each line in this file contains two fields separated by tabs or spaces. The first field is the logical archive directory prefix. The second field is the corresponding physical directory prefix.

Figure C-1 File Mapping Between Local and Archive Files

The cm.mapping file initially contains the following entry for the /TestArchive directory:

# TestArchive entry
/TestArchive  /var/tmp

In this entry, /TestArchive is the logical archive path by which the SoftBench CM client and server communicate, and /var/tmp is the physical path where the example files are stored on the SoftBench CM server.

Every file managed by SoftBench CM should have exactly one logical path name. You should not map multiple, logical archive path names to the same physical file or directory. When creating or updating the cm.mapping file, create the physical directories and set their ownership to softcm. Otherwise, the SoftBench CM server may not be able to access these directories. For example, if you add the following entry to the cm.mapping file:

#logical path   physical path
/project_95    /data/project_srcs

you would also need to do the following from the command line:

mkdir     /data/project_srcs
chown softcm /data/project_srcs
chgrp 10000  /data/project_srcs
chmod 700   /data/project_srcs

Change the group id number for the "chgrp" entry above if you used a GroupID number other than "10000" for the softcm entry in the /etc/passwd file.

You can edit the cm.mapping file while the SoftBench CM server is running. The server notices the changes and updates its internal data structures automatically.

Defining User Access to the Server

The cm.permission file determines users' access rights to the SoftBench CM archive files. When you make changes to this file, they take effect within 30 seconds of saving the file.

The cm.permission file consists of a series of entries. Each entry contains three types of fields terminated by a semicolon, as follows:

  f1 f2 f3 ... [ f2 f3 ... ] ... ;

where f1, f2 and f3 are three distinct types.

The permission symbols come in three groups:

SoftBench CM normally uses the best matching entry (longest /path prefix match, then most specific user/host match) to determine access rights. However, by specifying priorities, you can use a shorter path for a specific user. For example, in the following entries:

  *@host R /earth ;
  john@host S / ;
  jane@host 2S / ;

the user "john" has "R" access to /earth because /earth is more specific than "/" and "S" access to the rest of the archive. The user "jane" has "S" access to the whole archive, including /earth because the "2" specifies an increased priority.

The /opt/softbench/sbin/checkperm -d command displays the permissions file entries in sorted order. For any given access, the first entry that matches the requesting user@host and /path determines the access.

Recommended Format for Permissions File

You can order fields within an entry in two formats:

Format 1. Place user field first and permissions field second.

user1@host.domain.hp.com
      RM  /project1 /project2
      S    /project3    # system admin
      R    /                # read-only default
      ;
user2@hp*  S    /project1
      RM  /project2 /project3
      ;

Format 2. Place path field first and permissions field second.

/      R    *@*
      ;
/project1  RM   user1@host* user2@15.1.1-40.* user3@*
      S    user4@host1.domain.hp.com
      ;
/project2  RM   user1@host*
      RMD   user2@host1*
      ;

Use the pattern RMDA or -abf-cdilmnptuwx-oqz-esvy for permissions and replace the disallowed permission bits or groupings with "-" characters. This makes it easier to understand which permissions are deleted and given. The permission letters can be in any order.

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:

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.

You can edit the inetd.sec file while running the archive server. The server notices the change and updates its internal data structures immediately.