Platform LSF Reference Version 6.2

bkill
Platform LSF Reference
71
Using bkill on a repetitive job kills the current run, if the job has been started, and
requeues the job. See
bcadd(1) and bsub(1) for information on setting up a job to run
repetitively.
If the job cannot be killed, use
bkill -r to remove the job from the LSF system
without waiting for the job to terminate, and free the resources of the job.
OPTIONS
0
Kills all the jobs that satisfy other options (-g, -m, -q, -u, and -J).
-b
Kills large numbers of jobs as soon as possible. Local pending jobs are killed
immediately and cleaned up as soon as possible, ignoring the time interval specified by
CLEAN_PERIOD in
lsb.params. Jobs killed in this manner are not logged to
lsb.acct.
Other jobs, such as running jobs, are killed as soon as possible and cleaned up normally.
If the
-b option is used with the 0 subcommand, bkill kills all applicable jobs and
silently skips the jobs that cannot be killed.
% bkill -b 0
Operation is in progress
The -b option is ignored if used with the -r or -s options.
-l
Displays the signal names supported by bkill. This is a subset of signals supported by
/bin/kill and is platform-dependent.
-r
Removes a job from the LSF system without waiting for the job to terminate in the
operating system.
Sends the same series of signals as
bkill without -r, except that the job is removed
from the system immediately, the job is marked as EXIT, and the job resources that LSF
monitors are released as soon as LSF receives the first signal.
Also operates on jobs for which a
bkill command has been issued but which cannot
be reached to be acted on by
sbatchd (jobs in ZOMBI state). If sbatchd recovers
before the jobs are completely removed, LSF ignores the zombi jobs killed with
bkill
-r
.
Use
bkill -r only on jobs that cannot be killed in the operating system, or on jobs
that cannot be otherwise removed using
bkill.
The
-r option cannot be used with the -s option.
-g job_group_name
Operates only on jobs in the job group specified by job_group_name.
You cannot use
-g with -sla. A job can either be attached to a job group or a service
class, but not both.
bkill does not kill jobs in lower level job groups in the path. For example, jobs are
attached to job groups
/risk_group and /risk_group/consolidate: