Five practical applications of the Killall command that you may not know

Linux command lines provide many commands to kill processes. For example, you can pass a PID to kill the process. The pkill command uses a regular expression as the input, so all processes that match the pattern are killed. However, there is another command named killall. by default,

Linux command lines provide many commands to kill processes. For example, you can pass a PID to the "kill" command to kill the process. The "pkill" command uses a regular expression as the input, so all processes that match the pattern are killed.

However, there is another command named "killall". by default, it precisely matches the parameter name and then kills the matching process. In this article, we will discuss the practical application of this command.

 

Linux killall command

The Killall command can be used to send a signal to a specific process. This signal is SIGTERM by default, but other signals can also be specified by the killall command using parameters.

Now let's take a look at the actual usage of this command through some practical examples.

1. Basic example

In this example, killall is used to kill a specific process. Suppose there are two processes with the same starting characters:

 
 

  
  
___FCKpd___0nbsp;ps -aef | grep “test” 
  
  
himanshu 3969 2811 0 14:14 pts/0 00:00:00 ./test 
  
  
himanshu 3970 2811 0 14:14 pts/0 00:00:00 ./test_again 
 
 

How to kill the "test_again" process?

 
 

  
  
___FCKpd___1nbsp;killall test_again 
  
  
[2]+ Terminated ./test_again 
 
 

As you can see, the killall command terminates the "test_again" process. You can use the ps command to confirm this fact:

 
 

  
  
___FCKpd___2nbsp;ps -aef | grep “test” 
  
  
himanshu 3969 2811 0 14:14 pts/0 00:00:00 ./test 
 
 

You can see that "test_again" is not displayed because it has been killed.

2. use the-I option to ignore case sensitivity.

By default, the killall command is case sensitive. For example:

 
 

  
  
___FCKpd___3nbsp;ps -aef | grep “test” 
  
  
himanshu 4177 3161 0 14:54 pts/3 00:00:00 ./test 
  
  
himanshu 4178 3161 0 14:54 pts/3 00:00:00 ./test_again 
  
  
himanshu 4180 3161 0 14:54 pts/3 00:00:00 grep --color=auto test 
  
  
___FCKpd___3nbsp;killall TEST 
  
  
TEST: no process found 
 
 

You can see that the killall command cannot find the process named "TEST", but the "test" process is indeed running.

To make the killall command ignore case sensitivity. you can use the-I option (uppercase I ). For example:

 
 

  
  
___FCKpd___4nbsp;killall -I TEST 
  
  
[1]- Terminated ./test 
 
 

You can see that you have successfully terminated the "test" process.

3. use the-I option to terminate processes interactively.

The killall command can be used to terminate multiple processes.

 
 

  
  
___FCKpd___5nbsp;killall test test_again 
  
  
[2]- Terminated ./test_again 
  
  
[3]+ Terminated ./test 
 
 

However, if you want killall to terminate the process interactively, you can use the-I option.

Here is an example:

 
 

  
  
___FCKpd___6nbsp;killall -i test test_again 
  
  
Kill test(4201) ? (y/N) y 
  
  
Kill test_again(4202) ? (y/N) y 
  
  
[1]- Terminated ./test 
  
  
[2]+ Terminated ./test_again 
 
 

You can see that, in this way, when terminating multiple processes at the same time, the user can control whether to terminate a process.

4. use the-q option to disable command execution Echo

Sometimes, when killall cannot find the specified process, it will output an error message as follows.

 
 

  
  
___FCKpd___7nbsp;killall TEST 
  
  
TEST: no process found 
 
 

However, if you want to perform killall securely, you can use the-q option:

 
 

  
  
___FCKpd___8nbsp;killall -q TEST 
  
  
___FCKpd___8nbsp;
 
 

As you can see, after the-q option is used, the output information of the killall command is blocked.

5. use the-l option to list all supported signals (signal)

As described earlier, killall sends signals to processes.

You can use the-s option (followed by a signal name) to send a special signal to a process.

To know all the signals that can be sent, you can use the-l option (lower case L) to obtain:

 
 

  
  
___FCKpd___9nbsp;killall -l 
  
  
HUP INT QUIT ILL TRAP ABRT IOT BUS FPE KILL USR1 SEGV USR2 PIPE ALRM TERM 
  
  
STKFLT CHLD CONT STOP TSTP TTIN TTOU URG XCPU XFSZ VTALRM PROF WINCH IO PWR SYS 
  
  
UNUSED 
 
 

Killall supports all signals above.

Looking at the names of these signals, you may be wondering: What do these signals do?

Note: Use the following command to obtain the description of all signals:

 
 

  
  
___FCKpd___10nbsp;man 7 signal 
 
 

I need to discuss one thing with you.

The killall command man said: If the length of the process name is less than or equal to 15, the full name will be matched by default.

For example, suppose there are two processes with long names:

 
 

  
  
___FCKpd___11nbsp;ps -aef | grep “test” 
  
  
himanshu 4021 3161 0 14:27 pts/3 00:00:00 ./test_abcdefghij 
  
  
himanshu 4035 3161 0 14:27 pts/3 00:00:00 ./test_abcdefgh 
 
 

The name of the first process is 15 characters long. Now, let's try to use killall to kill the process:

 
 

  
  
___FCKpd___12nbsp;killall test_abcdefghij 
  
  
[1]- Terminated ./test_abcdefghij 
 
 

As you can see, the killall command successfully killed the process.

If the names of both processes exceed 15 characters, killall will kill all processes according to man. For example:

 
 

  
  
___FCKpd___13nbsp;ps -aef | grep “test” 
  
  
himanshu 4114 3161 0 14:40 pts/3 00:00:00 ./test_abcdefghijklmnopqrstuvwx 
  
  
himanshu 4141 3161 0 14:46 pts/3 00:00:00 ./test_abcdefghijklmnopqrstuvwxyz 
  
  
himanshu 4143 3161 0 14:46 pts/3 00:00:00 grep --color=auto test 
 
 

You can observe that the names of both processes are more than 15 characters long. Now, when I try to killall to kill the second process:

 
 

  
  
___FCKpd___14nbsp;killall test_abcdefghijklmnopqrstuvwxyz 
  
  
[6]+ Terminated ./test_abcdefghijklmnopqrstuvwxyz 
 
 

It only kills the specified process, and the other is not killed.

 
 

  
  
___FCKpd___15nbsp;ps -aef | grep “test” 
  
  
himanshu 4114 3161 0 14:40 pts/3 00:00:00 ./test_abcdefghijklmnopqrstuvwx 
  
  
himanshu 4146 3161 0 14:47 pts/3 00:00:00 grep --color=auto test 
 
 

I'm not sure. Is there something wrong with my attempt or is it a bug in killall. I would be very grateful if you wrote your opinion in the comment.

By the way, this is the version of the killall command on my machine:

 
 

  
  
___FCKpd___16nbsp;killall --version 
  
  
killall (PSmisc) 22.20 
  
  
Copyright (C) 1993-2012 Werner Almesberger and Craig Small 
  
  
PSmisc comes with ABSOLUTELY NO WARRANTY. 
  
  
This is free software, and you are welcome to redistribute it under 
  
  
the terms of the GNU General Public License. 
  
  
For more information about these matters, see the files named COPYING.