what to do when ctrl-c can't kill a process?

Question

Ctrl-c doesn't always work to kill the current process (for instance, if that process is busy in certain network operations). In that case, you just see "^C" by your cursor, and can't do much else.

What's the easiest way to force that process to die now without losing my terminal?

Summary of answers below: Usually, you can Ctrl-z to put the process to sleep, and then do "kill -9 process-pid", where you find the process's pid with 'ps' and other tools. On Bash (and possibly other shells) you can do "kill -9 %1" (or '%N' in general) which is easier. If Ctrl-z doesn't work, you'll have to open another terminal and kill from there.

Answer 1

to understand the problem of why ctrlc does not work it is very helpful to understand what happens when you press it:

most shells bind ctrlc to 'send the program that currently runs in the foreground a SIGINT signal'. you can read about the different signals via man signal:

 SIGINT        2       Term    Interrupt from keyboard

programs can ignore that signal. as they can ignore SIGTSTP as well:

 SIGTSTP   18,20,24    Stop    Stop typed at tty

(which is what most shells do when you press ctrlz, which is why it is not guaranteed to work)

there are some signals which can not be ignored by the process: SIGKILL, SIGSTOP and some others. you can send these signals via the kill command. so, to kill your hanging / zombieying process, just find out about the process id (PID), eg use pgrep or ps and then kill it:

 % kill -9 PID

Answer 2

Press Ctrl-Z to suspend the program and put it in the background:

Suspend the program currently running and put it in the background.
This does not stop the process as it does in VMS!

(Restore to foreground again using fg)

Then, you can kill or kill -9 it, given its process ID (you get that from ps a).

Answer 3

If Ctrl-C (SIGINT) doesn't work, try Ctrl-\ (SIGQUIT). Then try Ctrl-Z (and if that doesn't work go to another terminal or SSH session) and do kill -TERM on the process ID. Only as a last resort should you do kill -KILL, a.k.a. kill -9,as it doesn't give the process any chance to abort cleanly, sync its open files, close network connections, etc.

Answer 4

Usually you can still stop process (ctrl-z) and then use kill -9. For kill -9 you need process PID first. You can obtain that by running command

ps

Then you can run

kill -9 <appropriate pid from ps output>

Answer 5

1) If you are on the console and in multi-user mode, you could press CTRL-ALT-Fn and login on another screen, use ps -ef | grep <myprocessname> or pidof <myprocessname> and then kill -9 the process by ID number.

2) If you are connected remotely, do the same via another terminal session.

You could also make life a little easier by installing htop, which is a more versatile version of top that allows you to selectively kill running processes. Most distros have htop in a repo.

3) if you are just stuck in a hung ssh session (to another system, for example), try pressing tilde (~), which is the escape key, and then press CTRL-Z to drop back to the host session, then you can kill the stuck ssh process or wait for it to timeout, which most sill do after a period of inactivity.

Answer 6

See this link as well.

Ctrl+Z: pause a process.

Ctrl+C: politely ask the process to shut down now.

Ctrl+\: mercilessly kill the process that is currently in the foreground

Answer 7

A simpler solution for Bash (and other shells?) is to do:

Ctrl-z      followed by     kill -9 %1

where '%1' refers to the job number being killed. It might be '%2' (or something else) if you already have other jobs sleeping. You can see which job number it is when you hit Ctrl-z:

[1]+  Stopped                 <process name>

Note that 'kill' is the shell's version of kill, not /bin/kill.