One of the things I hate about Windows is that there is no good way to kill frozen processes. Theoretically, you type Ctrl-Alt-Delete, wait for Task Manager to pop up, and kill the process. But in reality, the process doesn't always die immediately (it usually takes multiple tries and a very long time). GNU/Linux users don't have this problem.

slay is a command line utility used for killing all the processes used by a particular User. Some users will leave with out logingout, some kid users will use heavy games and stay it in background. slay will kill all the processes for such conditions.

If you have a process ID but aren't sure whether it's valid, you can use the most unlikely of candidates to test it: the kill command.

Your GNU/Linux computer is an amazing machine. It can display images. It can run programs. It can perform dozens of functions all at the same time. How can you keep track of all this activity? By monitoring the processes that your computer runs, and one of the best ways to monitor and control processes is by using the command line.

A true wizard doesn’t just run processes, a true wizard knows how to communicate with those processes through signals to stop, restart, and even kill processes. This may sound like arcane and obscure knowledge, but if you follow along, you’ll be managing your processes like an adept in no time.

There are many ways to kill processes in Linux. Today I’m gonna share with you my favorite one. And the one I think is the easiest: xkill

The PSMon utility lets you specify which processes should be running, how much of resources such as CPU or RAM each is allowed to use when it runs, and how many instances are able to be run. PSMon will then ensure that these processes are running and kill off a process if it starts to use too many resources, and possibly restart a process if it has crashed.

It occurred to me that I was running 3 CPU-bound processes on the same machine and that the processes might be stepping on each other's toes. It's possible that if the server is running on core 4 one second and the producer is running there the next, the level 1 cache of that core could be ruined for the server the next time it ambles over there.

There are many different GUI based process monitors available for Linux systems. It seems that each desktop environment or window manager has its own solution. The one common process monitor is the command line terminal based top command.