Administering Platform LSF - SAS

Killing Jobs
Killing a job
Chapter 6
Managing Jobs
The bkill command cancels pending batch jobs and sends signals to running
jobs. By default, on UNIX, bkill sends the SIGKILL signal to running jobs.
Before SIGKILL is sent, SIGINT and SIGTERM are sent to give the job a chance
to catch the signals and clean up. The signals are forwarded from mbatchd to
sbatchd. sbatchd waits for the job to exit before reporting the status. Because
of these delays, for a short period of time after the bkill command has been
issued, bjobs may still report that the job is running.
On Windows, job control messages replace the SIGINT and SIGTERM signals,
and termination is implemented by the TerminateProcess() system call.
Run bkill job_ID:
% bkill 3421
Job is being terminated
kills job 3421.
Forcing removal of a job from LSF
Run bkill -r to force the removal of the job from LSF. Use this option when
a job cannot be killed in the operating system.
The bkill -r command removes a job from the LSF system without waiting
for the job to terminate in the operating system. This sends the same series of
signals as bkill without -r, except that the job is removed from the system
immediately, the job is marked as EXIT, and job resources that LSF monitors
are released as soon as LSF receives the first signal.
Administering Platform LSF 121