Options
Use
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:
bsub
Job <115> is submitted to default queue <normal>.
bsub
Job <116> is submitted to default queue <normal>.
The following bkill command only kills jobs in /risk_group, not the subgroup /risk_group/consolidate:
bkill
Job <115> is being terminated
bkill
Job <116> is being terminated
Operates only on jobs dispatched to the specified host or host group.
If job_ID is not specified, only the most recently submitted qualifying job is operated on. The
If job_ID is not specified, only the most recently submitted qualifying job is operated on.
The
See bqueues(1) for more information about queues.
Sends the specified signal to specified jobs. You can specify either a name, stripped of the SIG prefix (such as KILL), or a number (such as 9).
Eligible UNIX signal names are listed by bkill
The
Use bkill
Sending the SIGSTOP signal to sequential jobs or the SIGTSTP to parallel jobs is the same as using bstop.
You cannot suspend a job that is already suspended, or resume a job that is not suspended. Using SIGSTOP or SIGTSTP on a job that is in the USUSP state has no effect and using SIGCONT on a job that is not in either the PSUSP or the USUSP state has no effect. See bjobs(1) for more information about job states.
Operates on jobs belonging to the specified service class.
If job_ID is not specified, only the most recently submitted job is operated on.
78Platform LSF Command Reference