Platform LSF Reference Version 6.2

bkill
Platform LSF Reference
70
bkill
sends signals to kill, suspend, or resume unfinished jobs
SYNOPSIS
bkill [-l] [-g job_group_name |-sla service_class_name] [-J job_name]
[
-m host_name | -m host_group] [-q queue_name] [-r |
-s (signal_value | signal_name)] [-u user_name | -u user_group | -u all]
[job_ID ... |
0 | "job_ID[index]" ...]
bkill [-l] [-b] [-g job_group_name |-sla service_class_name] [-J job_name]
[
-m host_name | -m host_group] [-q queue_name] [-u user_name |
-u user_group | -u all] [job_ID ... | 0 | "job_ID[index]" ...]
bkill [-h | -V]
DESCRIPTION
By default, sends a set of signals to kill the specified jobs. On UNIX, SIGINT and
SIGTERM are sent to give the job a chance to clean up before termination, then
SIGKILL is sent to kill the job. The time interval between sending each signal is defined
by the JOB_TERMINATE_INTERVAL parameter in
lsb.params(5).
You must specify a job ID or
-g, -J, -m, -u, or -q. Specify job ID 0 (zero) to kill
multiple jobs.
On Windows, job control messages replace the SIGINT and SIGTERM signals (but
only customized applications can process them) and the
TerminateProcess()
system call is sent to kill the job.
Exit code 130 is returned when a dispatched job is killed with
bkill.
Users can only operate on their own jobs. Only
root and LSF administrators can
operate on jobs submitted by other users.
If a signal request fails to reach the job execution host, LSF tries the operation later when
the host becomes reachable. LSF retries the most recent signal request.
If a job is running in a queue with CHUNK_JOB_SIZE set,
bkill has the following
results depending on job state:
PEND
Job is removed from chunk (NJOBS -1, PEND -1)
RUN
All jobs in the chunk are suspended (NRUN -1, NSUSP +1)
USUSP
Job finishes, next job in the chunk starts if one exists (NJOBS -1, PEND -1, SUSP -1,
RUN +1)
WAIT
Job finishes (NJOBS-1, PEND -1)