Processes are required to respond to signals sent to them. This is one way a user can communicate with signals and control them.

htop is an improved version of top, a complex process viewer which allows to visualize processes in real time, see memory and CPU consumption, send signals to processes, renice processes, and sort them by various options. It makes use of colors and you can also scroll horizontally and vertically to see the full names of the running processes.

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.

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.

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.

One of the best features in Linux is the way you can control processes from the command line, so if you have an application that locks up your GUI, you can always SSH over from another machine and just kill the offending process.

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.

All modern operating systems are able to run many programs at the same time. For example, a typical Linux server might include a Web server, an email server, and probably a database service. Each of these programs runs as a separate process. What do you do if one of your services stops working? Here are some handy command-line tools for managing processes.