LSF Version 7.3 - Platform LSF Configuration Reference

•
Do not specify a signal followed by an action that triggers the same signal. For example,
do not specify TERMINATE_CONTROL=bkill. This causes a deadlock between the
signal and the action.
•
CHKPNT is a special action, which causes the system to checkpoint the job. The job is
checkpointed and killed automatically.
Description
Changes the behavior of the TERMINATE action in LSF.
•
The contents of the configuration line for the action are run with /bin/sh -c so you can
use shell features in the command.
•
The standard input, output, and error of the command are redirected to the NULL device,
so you cannot tell directly whether the command runs correctly. The default null device
on UNIX is /dev/null.
•
The command is run as the user of the job.
•
All environment variables set for the job are also set for the command action. The following
additional environment variables are set:
•
LSB_JOBPGIDS — a list of current process group IDs of the job
•
LSB_JOBPIDS —a list of current process IDs of the job
Default
•
On UNIX, by default, TERMINATE sends SIGINT, SIGTERM and SIGKILL in that order.
•
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. Termination is
implemented by the TerminateProcess() system call.
THREADLIMIT
Syntax
THREADLIMIT=integer
Description
Limits the number of concurrent threads that can be part of a job. Exceeding the limit causes
the job to terminate. The system sends the following signals in sequence to all processes belongs
to the job: SIGINT, SIGTERM, and SIGKILL.
By default, jobs submitted to the queue without a job-level thread limit are killed when the
thread limit is reached. Application-level limits override any default limit specified in the
queue.
The limit must be a positive integer.
Default
Unlimited
lsb.applications
186 Platform LSF Configuration Reference