CHAPTER 16 TAKING CONTROL (Web hosting unlimited bandwidth) OF THE SYSTEM
CHAPTER 16 TAKING CONTROL OF THE SYSTEM Note No magic is involved in killing processes. All that happens is that top sends them a terminate signal. In other words, it contacts them and asks them to terminate. By default, all processes are designed to listen for commands such as this; it s part and parcel of how programs work under Linux. When a program is described as crashed, it means that the user is unable to use the program itself to issue the terminate command (such as Quit). A crashed program might not be taking input, but its processes will probably still be running. In many cases, zombie processes simply won t go away. When this happens, you have two options. The first is to restart the program that is likely to be the zombie s owner, in the hope that it will reattach with the zombie, and then quit the program. With any luck, it will take the zombie child with it this time. Alternatively, you can simply reboot your PC. But it s important to note that zombie processes are harmless and can be left in peace on your system! Using Other Commands to Control Processes You don t always need to use top to control processes. A range of quick and cheerful shell commands can diagnose and treat process problems. The first of these is the ps command. This stands for Process Status and will report a list of currently running processes on your system. This command is normally used with the -aux options: ps aux This will return a list something like what you see when you run top. If you can spot the problematic process, look for its PID and issue the following command: kill