Platform LSF Reference Version 6.2

Parameters
Platform LSF Reference
566
See Also
LSF_NIOS_RES_HEARTBEAT
LSF_RES_DEBUG
Syntax
LSF_RES_DEBUG=1
| 2
Description
Sets RES to debug mode.
If LSF_RES_DEBUG is defined, the Remote Execution Server (RES) will operate in
single user mode. No security checking is performed, so RES should not run as root.
RES will not look in the services database for the RES service port number. Instead, it
uses port number 36002 unless LSF_RES_PORT has been defined.
Specify 1 for this parameter unless you are testing RES.
Valid values
◆ LSF_RES_DEBUG=1
RES runs in the background with no associated control terminal.
◆ LSF_RES_DEBUG=2
RES runs in the foreground and prints error messages to
tty.
Default
Undefined
See also
LSF_LIM_DEBUG, LSF_CMD_LOGDIR, LSF_CMD_LOG_MASK,
LSF_LOG_MASK, LSF_LOGDIR
LSF_RES_PLUGINDIR
Syntax
LSF_RES_PLUGINDIR=
path
Description
The path to lsbresvcl.so. Used only with SUN HPC.
Default
Path to LSF_LIBDIR
See also
LSF_PAM_PLUGINDIR, LSF_LIM_PLUGINDIR
LSF_RES_PORT
See “LSF_LIM_PORT, LSF_RES_PORT, LSB_MBD_PORT, LSB_SBD_PORT” on
page 555.
LSF_RES_RLIMIT_UNLIM
Syntax
LSF_RES_RLIMIT_UNLIM=cpu
| fsize | data | stack | core | vmem
Description
By default, RES sets the hard limits for a remote task to be the same as the hard limits
of the local process. This parameter specifies those hard limits which are to be set to
unlimited, instead of inheriting those of the local process.
Valid values are
cpu, fsize, data, stack, core, and vmem, for CPU, file size, data
size, stack, core size, and virtual memory limits, respectively.
Example
The following example sets the CPU, core size, and stack hard limits to be unlimited for
all remote tasks:
LSF_RES_RLIMIT_UNLIM="cpu core stack"
Default
Undefined
See also
LSF_LIM_SOL27_PLUGINDIR