Platform LSF Reference Version 6.2

lsf.conf
Platform LSF Reference
533
Description
Displays an abbreviated list of hosts in bjobs and bhist for a parallel job where
multiple processes of a job are running on a host. Multiple processes are displayed in the
following format:
processes*hostA
For example, if a parallel job is running 5 processes on hostA, the information is
displayed in the following manner:
5*hostA
Setting this parameter may improve mbatchd restart performance and accelerate event
replay.
Default
Undefined
LSB_SIGSTOP
Syntax
LSB_SIGSTOP=
signal_name | signal_value
Description
Specifies the signal sent by the SUSPEND action in LSF. You can specify a signal name
or a number.
If LSB_SIGSTOP is set to anything other than SIGSTOP, the SIGTSTP signal that is
normally sent by the SUSPEND action is not sent.
If this parameter is undefined, by default the SUSPEND action in LSF sends the
following signals to a job:
◆ Parallel or interactive jobs—1. SIGTSTP is sent first to allow user programs to catch
the signal and clean up. 2. SIGSTOP is sent 10 seconds after SIGTSTP. SIGSTOP
cannot be caught by user programs.
◆ Other jobs—SIGSTOP is sent. SIGSTOP cannot be caught by user programs.
The same set of signals is not supported on all UNIX systems. To display a list of the
symbolic names of the signals (without the SIG prefix) supported on your system, use
the
kill -l command.
Example LSB_SIGSTOP=SIGKILL
In this example, the SUSPEND action sends the three default signals sent by the
TERMINATE action (SIGINT, SIGTERM, and SIGKILL) 10 seconds apart.
Default
Undefined. Default SUSPEND action in LSF is sent.
LSB_SUB_COMMANDNAME
Syntax LSB_SUB_COMMANDNAME=y | Y
Description
If set, enables esub to use the variable LSB_SUB_COMMAND_LINE in the esub job
parameter file specified by the $LSB_SUB_PARM_FILE environment variable.
The LSB_SUB_COMMAND_LINE variable carries the value of the
bsub command
argument, and is used when
esub runs.
Example
esub
contains: