Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

When I try to exit from my Linux server I get the message:

There are stopped jobs.

: Is there a single command to kill these?

share|improve this question
Additional examples in thie U&L Q&A:… – slm Apr 12 '14 at 20:25
I had opposite problem now, it would not warn about stopped jobs when I quit the shell! Had to put shopt -s checkjobs in my .bashrc – Sam Watkins Jul 9 '14 at 5:59
up vote 52 down vote accepted

To quickly kill all the jobs running under the bash, enter:

kill `jobs -ps`

jobs -ps list process ID of the stopped jobs . kill `jobs -ps` send TERM signal to all stopped jobs.

share|improve this answer
-1 for "kill Jobs" – Tibor Aug 10 '12 at 21:44
didn't work when the job was "sudo su". i.e. sudo kill `jobs -p` didnt work but explicitly typing PID did. – user13107 Oct 27 '12 at 18:12
Why is this upvoted so highly? It's wrong. If the processes are stopped, then a kill such as this will do nothing, since the processes are stopped, they won't process the SIGTERM (-15) that is sent to them by default. – slm Apr 12 '14 at 20:18
kill -9 will do the trick. – Blossoming_Flower Oct 12 '14 at 17:36

Just in case this helps someone else -- most people are here because they have some stopped processes that they started, backgrounded via the shell maybe. I needed to find processes, as root, stopped by other users, for which variants on the jobs command won't do.

A bit of digging around with man ps got me to this:

ps -a -o pid,user,cmd,state | grep 'T$'

Explanation: the -a flag says show all processes, then -o controls output, what info will be shown about each process. I'm choosing pid, user, cmd (the command line), and state, which is the process state.

From man ps:

   Here are the different values that the s, stat and state output specifiers (header "STAT" or "S") will display to describe the
   state of a process:
           D    uninterruptible sleep (usually IO)
           R    running or runnable (on run queue)
           S    interruptible sleep (waiting for an event to complete)
           T    stopped, either by a job control signal or because it is being traced
           W    paging (not valid since the 2.6.xx kernel)
           X    dead (should never be seen)
           Z    defunct ("zombie") process, terminated but not reaped by its parent

so finally I pipe it to grep T$ which says, show me all the processes that have T in the last column.

And then I have a nice list of all the processes from different users that are in the stopped state.

$ ps -a -o pid,user,cmd,state | grep 'T$'
  865 joson74+ python                      T
  885 joson74+ sh -c less                  T
  886 joson74+ less                        T
 1014 minames+ python3.4 -i /home/minames  T
 5352 MooKo    nano stdio.h                T
 7851 harry    tmux attach                 T
12083 harry    tmux attach                 T
13495 gorylla+ python3.4 -i /home/gorylla1 T
18009 conr1d   vim                         T
19664 enythin+ python                      T
24906 wardlist python                      T
share|improve this answer

Normally if you got that message, you need to logout twice. E.g. first Ctrl+D gives you the warning message to inform you about stopped jobs, pressing for the second time will log you out killing the jobs. This the same applies to logout and exit commands.

To kill them manually, try: kill $(jobs -p).

If you don't want to kill jobs from your current shell, you can remove them from the table of active jobs without killing by using disown command. E.g.

$ sleep 1000 &
[1] 19404
$ jobs
[1]+  Running                 sleep 1000 &
$ disown

Stopped jobs also can be determined by the state of the process (T character) which means the process was stopped by signal such as SIGSTOP, SIGTSTP or other (like SIGTTIN, or SIGTTOU).

In case when jobs a shell builtin command is not available, stopped processes can be listed by the following command:

ps wuax | awk '$8 ~ "T"'

To kill them all, you can basically type:

kill -9 $(ps wuax | awk 'NR>1 && $8 ~ "T" {print $2}')

Here is a simple test:

$ sleep 1000 &
[1] 2014
$ sleep 1000 &
[2] 2015
$ sleep 1000 &
[3] 2016
$ sleep 1000 &
[4] 2017
$ killall -STOP sleep
[1]   Stopped                 sleep 1000
[2]   Stopped                 sleep 1000
[3]   Stopped                 sleep 1000
[4]   Stopped                 sleep 1000
$ ps wuax | awk '$8 ~ "T"'
vagrant   2014  0.0  0.0   7228   832 pts/0    T    20:38   0:00 sleep 1000
vagrant   2015  0.0  0.0   7228   708 pts/0    T    20:38   0:00 sleep 1000
vagrant   2016  0.0  0.0   7228   760 pts/0    T    20:38   0:00 sleep 1000
vagrant   2017  0.0  0.0   7228   828 pts/0    T    20:38   0:00 sleep 1000
$ kill -9 $(awk 'NR>1 && $8 ~ "T" {print $2}' <(ps wuax))
$ jobs
[1]   Killed                  sleep 1000
[2]   Killed                  sleep 1000
[3]   Killed                  sleep 1000
[4]   Killed                  sleep 1000
share|improve this answer

If you want to remove some stopped jobs but not all, try this:

First, list jobs, you will get something like this:

$ jobs -l

[2]   4813 Stopped                 ./parse < call.txt
[3]-  4819 Stopped                 ./parse < call.txt

send kill to a stopped job, it will do nothing but queue than bring it in in foreground, it will terminate

$ fg %2
./parse < call.txt

$ jobs -l
[3]-  4819 Stopped                 ./parse < call.txt
share|improve this answer
for x in `jobs -p` ; do kill -9 $x ; done
share|improve this answer
you can add code formatting for this line to make it easier to read. – drcelus Feb 26 '13 at 10:54
Can you take a look at your formatting again - use four spaces at the start of the line to mark a block as code (rather than using backtick). Right now it isn't clear whether you are using backticks in your code, or trying to display code using backticks. – dunxd Feb 26 '13 at 11:39
The formatting is fine. we have to pass the jobs -p using backticks else it wont consider as a command, and it will throw an error. – monu Feb 27 '13 at 6:01

The easiest way is actually to simply immediately retry the exit; bash will take that to mean "kill all stopped jobs and exit".

share|improve this answer
That will send a HUP which doesn't necessarily stop any jobs. – Stephen Niedzielski Jun 28 '14 at 2:27

The accepted answer would kill all jobs (which is sufficient in this case) and not merely the stopped ones. Should you want to kill only the Stopped ones, run:

kill $(jobs -l | grep Stopped | cut -d' ' -f3)
share|improve this answer
grep/cut can be combined in one awk command: awk '/Stopped/{print $3}') – laebshade Oct 20 '15 at 13:35

Try typing this:

kill -9 $(jobs -p)
share|improve this answer
That should do it, but I think he should send first a SIGTERM (-15) before sending a SIGKILL (-9). So perhaps proposing something like "kill $(jobs -p) ; sleep 3s ; kill -9 $(jobs -p)" would be better. Sending SIGTERM first the jobs may be able to do a clean exit (freeing allocated resources, etc). – rems Feb 25 '11 at 10:49
Kevin Duke, your answer is the one that worked for me. I couldn't vote because I don't have 15 in reputation. kill -9 $(jobs -p) – user131776 Aug 10 '12 at 21:33
@rems Except, as slm pointed out, they won't get the SIGTERM because they're stopped. – Paul Gear Jul 22 '14 at 23:59

protected by Sven Feb 6 '15 at 8:39

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site.

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.