Name

site file -- Cplant site configuration file

Description

Certain runtime configuration information required by yod, pct, a nd bebopd can be set up in a text file. For every item that can be defined in the site file, there is als o an environment variable that can define this item, and there is a de fault coded into the Cplant utilities and daemons. Definition of the i tems at runtime procedes like this: If there is an environment value defining the item, this is the v alue used.
Else if there is a definition in the site file, this is the value used.
Else the default coded into the utilities and daemons is used. The format of the site file is to list the environment variable n ame followed by the definition of the environment variable. Values that can be defined in the site file or by way of environm ent variables are the following:

PCT_SCRATCH

The path name to a directory in RAM disk on the compute nodes whe re the PCT will store the user's executable. Default: /tmp/pct-scratch

PCT_OVERFLOW

The path name to local disk on the compute node where the PCT can store user executables that don't fit in RAM disk. A value CRnone tells the PCT there is no disk storage for user executables. Default: none

LOGFILENAME

The pathname from the service node to the user log file written b y yod. Default: /tmp/userlog

VM_NAME_FILE

The pathname (from compute and service nodes) to a text file cont aining the name of the current virtual machine. Default: /cplant/etc/vmname

PBS_PREFIX

The location of the bin and sbin directories containi ng PBS executables. Default: /

The following values are used by yod when it tries to load an exe cutable that is too large to fit in the compute node RAM disk. yod inste ad copies the executable to the SSS1, and then uses the SUID yod_site_pri v to rsh to SSS1 and rcp the executable to the SSS0's on SUs which contain compute nodes of the job. yod tells the PCTs the pathname to these copie s of the executable and the PCTs exec them from there. (If all the comput e nodes of the job are in one SU, then yod just copies the executable to the SSS1 and tells the PCTs to exec it from there.) A CR%s in these definitions is replaced at runtime with the virtual mac hine name.

VM_GLOBAL_STORAGE

The path name on the SSS1 to a directory where the executable wil l be stored. Default: /usr/local/%s

VM_GLOBAL_STORAGE_FROM_SRV_NODE

The path name to VM_GLOBAL_STORAGE from the service nodes. Default: /etc/local

SU_GLOBAL_STORAGE

The path name on the SSS0 to a directory where the executable wil l be stored. Default: /cplant/nfs-cplant

LOCAL_EXEC_PATH

The path name to SU_GLOBAL_STORAGE from the compute node. Default: /cplant

SINGLE_LEVEL_GLOBAL_STORAGE

The path name to global storage on the SSS1 from the service node s. If all the compute nodes of a job are in one SU, a single copy of the executable will be made by yod to the directory on the SSS1. Default: /etc/local

SINGLE_LEVEL_LOCAL_EXEC_PATH

The path name to SINGLE_LEVEL_GLOBAL_STORAGE from the compute nod es. Default: /usr/local/%s

SU_NAME_FORMAT

At runtime, an SU machine name is formed by replacing CR%d in this format with the SU number. It is the machine name used in the rc p from the SSS1 to the SSS0. Default: z-%d

VM_GLOBAL_MACHINE

The machine name of the SSS1, for yod's rsh from the service node . Default: alaska-sss1-0

The default location of the site file is CR/etc/local/site. This can b e overridden at runtime with the environment variable SITE_FILE.

Table of Contents

• Name
• Description