Platform LSF Reference Version 6.2

bstop
Platform LSF Reference
148
bstop
suspends unfinished jobs
SYNOPSIS
bstop [-a] [-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] [0] [job_ID ... | "job_ID[index]"] ...
bstop [-h | -V]
DESCRIPTION
Suspends unfinished jobs.
Sends the SIGSTOP signal to sequential jobs and the SIGTSTP signal to parallel jobs
to suspend them.
You must specify a job ID or
-g, -J, -m, -u, or -q. You cannot suspend a job that is
already suspended. Specify job ID
0 (zero) to stop multiple jobs.
Only
root and LSF administrators can operate on jobs submitted by other users.
Use
bresume to resume suspended jobs.
Using
bstop on a job that is in the USUSP state has no effect.
You can also use
bkill -s STOP to send the suspend signal to a job or use
bkill -s TSTP to suspend one or more parallel jobs. Use bkill -s CONT to send
a resume signal to a job.
If a signal request fails to reach the job execution host, LSF will retry the operation later
when the host becomes reachable. LSF retries the most recent signal request.
OPTIONS
0
Suspends all the jobs that satisfy other options (-g, -m, -q, -u, and -J).
-a
Suspends all jobs.
-g job_group_name
Suspends 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.
-J job_name
Suspends only jobs with the specified name.
-m host_name | -m host_group
Suspends only jobs dispatched to the specified host or host group.
-q queue_name
Suspends only jobs in the specified queue.