To kill all the processes that you have the permission to kill, simply run the command
kill -15 -1 or kill -9 -1 depending on the desired behavior (use man kill for details)
To kill a specific process, say, firefox, simply run
pkill firefox or killall firefox depending on the behavior you want: What's the difference between 'killall' and 'pkill'?
If you want to see what processes are running use the command
ps -ef
If you want to look up all processes by user bob, this might help
pgrep -l -u bob
or
ps -ef | grep bob
Answer from ste_kwr on askubuntu.comBest way to effectively kill a process?
bash - How to kill a process by its pid on Linux? - Stack Overflow
Linux Mint - How do I force quit apps and programs when frozen?
Is there something like Task Manager for Mint?
Videos
To kill all the processes that you have the permission to kill, simply run the command
kill -15 -1 or kill -9 -1 depending on the desired behavior (use man kill for details)
To kill a specific process, say, firefox, simply run
pkill firefox or killall firefox depending on the behavior you want: What's the difference between 'killall' and 'pkill'?
If you want to see what processes are running use the command
ps -ef
If you want to look up all processes by user bob, this might help
pgrep -l -u bob
or
ps -ef | grep bob
Use:
kill <pid>
or:
killall <process-name>
There are different options to kill a proces like hangup, terminate or interrupt (to name a few) but which one is the most effective way of killing a process? Like is there a command with which you can eliminate nasty hard-frozen processes? Sorry if this question sounds dumb, I am just unsure on all the different kill-options and wanted to know the real difference between for example hangup and interrupt - thanks in advance! :)
use the following command to display the port and PID of the process:
sudo netstat -plten
AND THEN
kill -9 PID
Here is an example to kill a process running on port 8283 and has PID=25334

Instead of this:
proid= pidof $proceso
You probably meant this:
proid=$(pidof $proceso)
Even so,
the program might not get killed.
By default, kill PID sends the TERM signal to the specified process,
giving it a chance to shut down in an orderly manner,
for example clean up resources it's using.
The strongest signal to send a process to kill without graceful cleanup is KILL, using kill -KILL PID or kill -9 PID.
I believe it's some kind of problem with the bash language (which I just started learning).
The original line you posted, proid= pidof $proceso should raise an error,
and Bash would print an error message about it.
Debugging problems starts by reading and understanding the error messages the software is trying to tell you.