Skip to main content

qbinterrupt

Description

qbinterrupt requests the Supervisor to force a job off a host immediately killing it. The job is then placed back in the queue to be executed on another qualified host..

Usage

qbinterrupt [options] jobID... | 0

where JobID is one or more job IDs, and 0 is a wild card token representing all the user's jobs.

Options

OptionDescription
--runningInterrupt running jobs
--pendingInterrupt pending jobs
--subjobrunningInterrupt running subjobs
--subjobpendingInterrupt pending subjobs
--activeInterrupt active (pending,running,blocked) jobs
--user stringInterrupt jobs for user string
--type string --prototype stringInterrupt jobs with string type
--status stringInterrupt jobs with string status (ex. pending)
--name stringInterrupt jobs with string name
--kind stringInterrupt jobs of string kind
--pid intInterrupt jobs with process ID int
--pgrp intInterrupt jobs in int process group
--priority intInterrupt jobs with int priority
--cluster stringInterrupt jobs in string cluster
--cpus intInterrupt jobs with a total of int subjobs
--xmlOutput in XML format
--helpCommand help
--versionCommand version

Notes

This command only works on jobs which are already in the running state.

In order to kill jobs, the user must have either of the following qube privileges:

  • interrupt
  • admin

Refer to User Permissions or qbusers for more detail on the Qube! permission scheme

Examples

Interrupt only subjob 12354.0:

% qbinterrupt 12354.0

Interrupt all subjobs in 12345:

% qbinterrupt 12345

Interrupt all of anthony's jobs:

% qbinterrupt --user anthony 0

Interrupt all of anthony's jobs which are running:

% qbinterrupt --running --user anthony 0

See also

qbkill