Platform LSF Administration Guide Version 6.2

Chapter 34
Configuring Job Controls
Administering Platform LSF
507
❖ The scheduling thresholds of the queue and the execution host
◆ A closed run window of the queue opens again
◆ A preempted job finishes
TERMINATE action
Terminate a job. This usually causes the job change to EXIT status. The default action
is to send SIGINT first, then send SIGTERM 10 seconds after SIGINT, then send
SIGKILL 10 seconds after SIGTERM. The delay between signals allows user programs
to catch the signals and clean up before the job terminates.
To override the 10 second interval, use the parameter
JOB_TERMINATE_INTERVAL in the
lsb.params file. See the Platform LSF
Reference for information about the
lsb.params file.
LSF invokes the TERMINATE action when:
◆ The user or LSF administrator issues a bkill or brequeue command to the job
◆ The TERMINATE_WHEN parameter in the queue definition (lsb.queues)
causes a SUSPEND action to be redirected to TERMINATE
◆ The job reaches its CPULIMIT, MEMLIMIT, RUNLIMIT or PROCESSLIMIT
If the execution of an action is in progress, no further actions are initiated unless it is the
TERMINATE action. A TERMINATE action is issued for all job states except PEND.
Windows job control actions
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 will be able to process them. Termination is
implemented by the
TerminateProcess() system call.
See Using the Platform LSF SDK for more information about LSF signal handling
on Windows.