LSF Version 7.3 - Platform LSF Configuration Reference

after being suspended by LSF. For example, SUSPEND_CONTROL=bkill
$LSB_JOBPIDS; command
Default
On UNIX, by default, SUSPEND sends SIGTSTP for parallel or interactive jobs and
SIGSTOP for other jobs.
On Windows, actions equivalent to the UNIX signals have been implemented to do the
default job control actions. Job control messages replace the SIGINT and SIGTERM
signals, but only customized applications are able to process them.
SWAPLIMIT
Syntax
SWAPLIMIT=integer
Description
Limits the amount of total virtual memory limit for the job.
This limit applies to the whole job, no matter how many processes the job may contain.
Application-level limits override any default limit specified in the queue.
The action taken when a job exceeds its SWAPLIMIT or PROCESSLIMIT is to send SIGQUIT,
SIGINT, SIGTERM, and SIGKILL in sequence. For CPULIMIT, SIGXCPU is sent before
SIGINT, SIGTERM, and SIGKILL.
By default, the limit is specified in KB. Use LSF_UNIT_FOR_LIMITS in lsf.conf to specify
a larger unit for the the limit (MB, GB, TB, PB, or EB).
Default
Unlimited
TERMINATE_CONTROL
Syntax
TERMINATE_CONTROL=signal | command | CHKPNT
Remember:
Unlike the JOB_CONTROLS parameter in lsb.queues, the
TERMINATE_CONTROL parameter does not require square
brackets ([ ]) around the action.
signal is a UNIX signal name (for example, SIGTERM). The specified signal is sent to the
job. 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.
command specifies a /bin/sh command line to be invoked.
Do not quote the command line inside an action definition.
lsb.applications
Platform LSF Configuration Reference 185