| TORQUE Resource Manager |
Appendix C: Node Manager (MOM) Configuration
- C.1 Parameters
- C.2 Node Features and Generic Consumable Resource Specification
- C.3 Command Line Arguments
C.1 Parameters
| parameter | format | description | example |
| arch | <STRING> | specifies the architecture of the local machine. This information is used by the scheduler only. | arch ia64 |
| $clienthost | <STRING> | specifies the machine running pbs_server (NOTE: This parameter is deprecated, use pbsserver) | $clienthost node01.teracluster.org |
| $configversion | <STRING> | specifies the version of the config file data | $configversion 113 |
| $cputmult | <FLOAT> | cpu time multiplier. NOTE: if set to 0.0, MOM level cputime enforcement is disabled. | $cputmult 2.2 |
| $ideal_load | <FLOAT> | ideal processor load | $ideal_load 4.0 |
| $ignwalltime | <BOOLEAN> | ignore walltime (do not enable mom based walltime limit enforcement) | $ignwalltime true |
| $job_output_file_umask | <STRING> | uses the specified umask when creating job output and error files. Values can be specified in base 8, 10, or 16; leading 0 implies octal and leading 0x or 0X hexadecimal. A value of "userdefault" will use the user's default umask. This parameter is in version 2.3.0 and later. | $job_output_file_umask 027 |
| $logevent | <STRING> | specifies a bitmap for event types to log | $logevent 255 |
| $loglevel | <INTEGER> | specifies the verbosity of logging with higher numbers specifying more verbose logging. Values may range between 0 and 7. | $loglevel 4 |
| $log_file_max_size | <INTEGER> | Soft limit for log file size in kilobytes. Checked every 5 minutes. If the log file is found to be greater than or equal to log_file_max_size the current log file will be moved from X to X.1 and a new empty file will be opened. | $log_file_max_size = 100 |
| $log_file_roll_depth | <INTEGER> | specifies how many times a log fill will be rolled before it is deleted. | $log_file_roll_depth = 7 |
| $max_load | <FLOAT> | maximum processor load | $max_load 4.0 |
| $node_check_script | <STRING> | specifies the fully qualified pathname of the health check script to run. (see Health Check for more information) | $node_check_script /opt/batch_tools/nodecheck.pl |
| $node_check_interval | <INTEGER> | specifies the number of MOM intervals between subsequent executions of the specified health check. This value default to 1 indicating the check is run every mom interval. (see Health Check for more information) | $node_check_interval 5 |
| $nodefile_suffix | <STRING> | Specifies the suffix to append to a host names to denote the data channel network adapter in a multihomed compute node. | $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. |
| opsys | <STRING> | specifies the operating system of the local machine. This information is used by the scheduler only. | opsys RHEL3 |
| $pbsclient | <STRING> | specifies machines which the mom daemon will trust to run resource manager commands via momctl. This may include machines where monitors, schedulers, or admins require the use of this command.) | $pbsclient node01.teracluster.org |
| $pbsserver | <STRING> | specifies the machine running pbs_server (NOTE: This parameter replaces the deprecated parameter clienthost) | $pbsserver node01.teracluster.org |
| $prologalarm | <INTEGER> | Specifies maximum duration (in seconds) which the mom will wait for the job prolog or job job pilog to complete. This parameter default to 300 seconds (5 minutes) | $prologalarm 60 |
| $rcpcmd | <STRING> | specifies the full path and optional additional command line args to use to perform remote copies | |
| $remote_reconfig | <STRING> | Enables the ability to remotely reconfigure pbs_mom with a new config file. Default is disabled. This parameter accepts various forms of true, yes, and 1. | $remote_reconfig true |
| $restricted | <STRING> | Specifies hosts which can be trusted to access mom services as non-root. By default, no hosts are trusted to access mom services as non-root. | $restricted *.teracluster.org |
| size[fs=<FS>] | N/A | Specifies that the available and configured disk space in the <FS> filesystem is to be reported to the pbs_server and scheduler. NOTE: To request disk space on a per job basis, specify the file resource as in 'qsub -l nodes=1,file=1000kb' NOTE: 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 | <STRING> | Specifies whether or not mom will source the /etc/profile, etc. type files for batch jobs. Parameter accepts various forms of true, false, yes, no, 1 and 0. Default is True. This parameter is in version 2.3.1 and later. | $source_login_batch False mom will bypass the sourcing of /etc/profile, etc. type files. |
| $source_login_interactive | <STRING> | Specifies whether or not mom will source the /etc/profile, etc. type files for interactive jobs. Parameter accepts various forms of true, false, yes, no, 1 and 0. Default is True. This parameter is in version 2.3.1 and later. | $source_login_interactive False mom will bypass the sourcing of /etc/profile, etc. type files. |
| $status_update_time | <INTEGER> | Specifies the number of seconds between subsequent mom-to-server update reports. Default is 45 seconds | mom will send server update reports every 120 seconds. |
| $timeout | <INTEGER> | Specifies the number of seconds before mom-to-mom messages will timeout if RPP is disabled. Default is 60 seconds | timeout 120 mom-to-mom communication will allow up to 120 seconds before timing out. |
| $tmpdir | <STRING> | Specifies a directory to create job-specific scratch space (see Creating Per-Job Temporary Directories | $tmpdir /localscratch |
| $usecp | <HOST>:<SRCDIR> <DSTDIR> | Specifies which directories should be staged (see TORQUE Data Management) | $usecp *.fte.com:/data /usr/local/data |
| $wallmult | <FLOAT> | wall time multiplier. NOTE: if set to 0.0, MOM level walltime enforcement is disabled. | $wallmult 2.2 |
C.2 Node Features and Generic Consumable Resource Specification
Node features (a.k.a. node properties) are opaque labels which can be applied to a node. They are not consumable and cannot be associated with a value. (use generic resources described below for these purposes). Node features are configured within the global nodes file on the pbs_server head node and are not specified on a per node basis. This file can be used to specify an arbitrary number of node features.Additionally, per node consumable generic resources may be specified using the format '<ATTR> <VAL>' with no leading dollar ('$') character. When specified, this information is routed to the scheduler and can be used in scheduling decisions. For example, to indicate that a given host has two tape drives and one node-locked matlab license available for batch jobs, the following could be specified:
Dynamic Consumable Generic Resources
Dynamic consumable resource information can be routed in by specifying a value preceded by a exclamation point (i.e., '!') as in the example below. If the resource value is configured in this manner, the specified file will be periodically executed to load the effective resource value. (See section 2.5.3 of the 'PBS Administrator Guide' for more information)
C.3 Command Line Arguments
See Also