bstop

suspends unfinished jobs

Synopsis

bstop [-a] [-app application_profile_name] [-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.

By default, 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.

An administrator can use bstop on a job stopped by the user (in the state USUSP) to prevent the user from resuming the job.

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 retries 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.

-app application_profile_name

Suspends only jobs associated with the specified application profile. You must specify an existing application profile.

-g job_group_name

Suspends only jobs in the specified job group.

-J job_name

Suspends only jobs with the specified name.

The job name can be up to 4094 characters long. Job names are not unique.

The wildcard character (*) can be used anywhere within a job name, but cannot appear within array indices. For example job* returns jobA and jobarray[1], *AAA*[1] returns the first element in all job arrays with names containing AAA, however job1[*] will not return anything since the wildcard is within the array index.

-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.

-sla service_class_name

Suspends jobs belonging to the specified service class.

Use bsla to display the properties of service classes configured in LSB_CONFDIR/cluster_name/configdir/lsb.serviceclasses (see lsb.serviceclasses(5)) and dynamic information about the state of each configured service class.

-u user_name | -u user_group | -u all

Suspends only jobs owned by the specified user or user group, or all users if the keyword all is specified. To specify a Windows user account, include the domain name in uppercase letters and use a single backslash (DOMAIN_NAME\user_name) in a Windows command line or a double backslash (DOMAIN_NAME\\user_name) in a UNIX command line.

job_ID ... | "job_ID[index]" ...

Suspends only the specified jobs. Jobs submitted by any user can be specified here without using the -u option.

-h

Prints command usage to stderr and exits.

-V

Prints LSF release version to stderr and exits.

Examples

bstop 314

Suspends job number 314.

bstop -m hostA

Suspends the invoker’s last job that was dispatched to host hostA.

bstop -u jsmith 0

Suspends all the jobs submitted by user jsmith.

bstop -u all 

Suspends the last submitted job in the LSF system.

bstop -u all 0 

Suspends all jobs for all users in the LSF system.

bstop -g /risk_group/consolidate 0

Suspends all jobs in the job group /risk_group/consolidate.

bstop -app fluent 0

Suspends all jobs associated with the application profile fluent.

See also

bsub(1), bjobs(1), bqueues(1), bhosts(1), bresume(1), bkill(1), bapp(1), bgadd(1), bgdel(1), bjgroup(1), bparams(5), mbatchd(8), kill(1), signal(2) lsb.params(5)