bkill
bkill
sends signals to kill, suspend, or resume unfinished jobs
Synopsis
bkill
bkill
bkill
Description
By default, sends a set of signals to kill the specified jobs. On UNIX, SIGINT and SIGTERM are sent to give the job a chance to clean up before termination, then SIGKILL is sent to kill the job. The time interval between sending each signal is defined by the JOB_TERMINATE_INTERVAL parameter in lsb.params(5).
By default, kills the last job submitted by the user running the command. You must specify a job ID or
On Windows, job control messages replace the SIGINT and SIGTERM signals (but only customized applications can process them) and the TerminateProcess() system call is sent to kill the job.
Exit code 130 is returned when a dispatched job is killed with bkill.
Only root and LSF administrators can run bkill
Users can only operate on their own jobs. Only root and LSF administrators can operate on jobs submitted by other users.
If a signal request fails to reach the job execution host, LSF tries the operation later when the host becomes reachable. LSF retries the most recent signal request.
If a job is running in a queue with CHUNK_JOB_SIZE set, bkill has the following results depending on job state:
PEND
Job is removed from chunk (NJOBS
RUN
All jobs in the chunk are suspended (NRUN
76Platform LSF Command Reference