When set to TRUE, specifies that you want TORQUE to attempt to create the output directories for jobs if they do not already exist.

Default is FALSE.

TORQUE uses this parameter to make the directory as the user and not as root. TORQUE will create the directory (or directories) ONLY if the user has permissions to do so.

Specifies the machine running pbs_server.

This parameter is deprecated. Use $pbsserver.

CPU time multiplier.

If set to 0.0, MOM level cputime enforcement is disabled.

(Available in TORQUE 2.5.10, 3.0.4, and later.) Specifies the number of times to retry checking the password. Useful in cases where external password validation is used, such as with LDAP.

The default value is 3 retries.

This sets the connection timeout on the MOM to .3 seconds..

(Applicable in version 3.0 and later.) The memory_pressure of a cpuset provides a simple per-cpuset running average of the rate that the processes in a cpuset are attempting to free up in-use memory on the nodes of the cpuset to satisfy additional memory requests. The memory_pressure_threshold is an integer number used to compare against the reclaim rate provided by the memory_pressure file. If the threshold is exceeded and memory_pressure_duration is set, then the process terminates after exceeding the threshold by the number of times set in memory_pressure_duration. If memory_pressure duration is not set, then a warning is logged and the process continues. Memory_pressure_threshold is only valid with memory_pressure enabled in the root cpuset.

To enable, log in as the super user and execute the command echo 1 >> /dev/cpuset/memory_pressure_enabled. See the cpuset man page for more information concerning memory pressure.

$mom_hierarchy_retry_time 30

Specifies the number of MOM intervals between subsequent executions of the specified health check. This value defaults to 1 indicating the check is run every MOM interval (see Compute node health check for more information).

$node_check_interval has two special strings that can be set:

• jobstart – makes the node health script run when a job is started (before the prologue script).
• jobend – makes the node health script run after each job has completed on a node (after the epilogue script).

The node health check may be configured to run before or after the job with the "jobstart" and/or "jobend" options. However, the job environment variables do not get passed to node health check script, so it has no access to those variables at any time.

$nodefile_suffix i

with the suffix of "i" and the control channel adapter with the name node01, the data channel would have a hostname of node01i.

If this is configured, the job's output is spooled in the working directory of the job or the specified output directory.

Specify the list in full paths, delimited by commas. If the job's working directory (or specified output directory) is in one of the paths in the list (or a subdirectory of one of the paths in the list), the job is spooled directly to the output location. $nospool_dir_list * is accepted.

The user that submits the job must have write permission on the folder where the job is written, and read permission on the folder where the file is spooled.

Alternatively, you can use the $spool_as_final_name parameter to force the job to spool directly to the final output.

This should generally be used only when the job can run on the same machine as where the output file goes, or if there is a shared filesystem. If not, this parameter can slow down the system or fail to create the output file.

Specifies the machine running pbs_server.

This parameter replaces the deprecated parameter $clienthost.

If set to TRUE, jobs will be rejected and the user will receive the message, "Jobs cannot be run on mom %s." Default is FALSE.

$rpp_throttle 100

(will cause a 100 microsecond sleep)

Specifies that the available and configured disk space in the <FS> filesystem is to be reported to the pbs_server and scheduler.

To request disk space on a per job basis, specify the file resource as in qsub -l nodes=1,file=1000kb.

Unlike most MOM config options, the size parameter is not preceded by a "$" character.

size[fs=/localscratch]

The available and configured disk space in the /localscratch filesystem will be reported.

$source_login_batch False

MOM will bypass the sourcing of /etc/profile, etc. type files.

$source_login_interactive False

MOM will bypass the sourcing of /etc/profile, etc. type files.

status_update_time:

$status_update_time 120

MOM will send server update reports every 120 seconds.

thread_unlink_calls:

$thread_unlink_calls true

Specifies the number of seconds before a TCP connection on the MOM will timeout. Default is 300 seconds.

In version 3.x and earlier, this specifies the number of seconds before MOM-to-MOM messages will timeout if RPP is disabled. Default is 60 seconds.

$timeout 120

A TCP connection will wait up to 120 seconds before timing out.

For 3.x and earlier, MOM-to-MOM communication will allow up to 120 seconds before timing out.

Indicates that the user would like to use SMT. If set, each logical core inside of a physical core will be used as a normal core for cpusets. This parameter is on by default.

If SMT is used, you will need to set the np attribute so that each logical processor is counted.

Provides a way to keep track of dynamic attributes on nodes.

<INTEGER> is how many seconds should go by between calls to the script to update the dynamic values. If set to -1, the script is read only one time.

<STRING> is the script path. This script should check for whatever dynamic attributes are desired, and then output lines in this format:

name=value

Include any arguments after the script's full path. These features are visible in the output of pbsnodes-a

varattr=Matlab=7.1;Octave=1.0.

For information about using $varattr to request dynamic features in Moab, see Configuring dynamic features in TORQUE and Moab in the Moab Workload Manager Administrator Guide.

Sets a factor to adjust walltime usage by multiplying a default job time to a common reference system. It modifies real walltime on a per-MOM basis (MOM configuration parameters). The factor is used for walltime calculations and limits in the same way that cputmult is used for cpu time.

If set to 0.0, MOM level walltime enforcement is disabled.