Kill undisciplined processes of Unix operating systems

Article Title: Killing processes that do not discipline Unix operating systems. Linux is a technology channel of the IT lab in China. Includes basic categories such as desktop applications, Linux system management, kernel research, embedded systems, and open source.

I wrote the following in linux.chinaitlab.com/administer/780117.html "target = _ blank>Properly manage processes and make them the patron saint of Unix systemsIn this article, processes are the patron saint of Unix systems. However, sometimes this patron saint is also awkward and will be against the Unix operating system. If the task has been completed, but the process has not been completed properly. Or the process occupies a large amount of system resources for no reason, leading to slow down the system speed and affecting the normal operation of other jobs. System Engineers can only pick up the knives in their hands and implement the "no harm" policy.

There are multiple methods in Unix to kill these abnormal processes. In general, I suggest that the process should be killed in an orderly manner and try to adopt methods that have little impact on the operating system.

　Stage 1: Kill the process on the local machine.

System Engineers can directly interrupt commands on Unix systems and use related commands to kill abnormal processes. For example, you can press the DEL key, Ctrl + D key, and Break key on the disk to kill the process. Any one of these keys by a system engineer sends an interruption signal to the system process. Note: Generally, only the root user can kill other supported processes or system processes. Other users can only kill their own processes. For example, you need to deploy an Oracle database server in a Unix system. For ease of management, Unix System Engineers set up an Oracle user to maintain and manage the database system. In this case, the Oracle user runs several processes, such as tns. Under normal circumstances, Oracle users and root users can kill this process. However, if there are other users in the system, the process cannot be killed.

In addition, if the process you want to kill is a shell sub-process, you can also kill the job number of the home process. For example, kill % job number. Shell is a good interaction tool in Unix systems. It is also called the command line interface, which is the interaction section of the most traditional and historical users and computers in Unix operating systems. The system administrator can directly enter related commands here to execute various maintenance tasks, including killing abnormal processes. In fact, it is very similar to the command line interface in the Microsoft operating system, but there are some differences. For example, a shell in a Unix operating system is both a user-system interaction interface and a script language used to control the system. This is the biggest difference between the two. An important feature of Shell is to hide the underlying details of the operating system, so it is the first choice for engineers to maintain the system.

In fact, most of the time engineers manage processes in shell environments, including viewing process information in the previous article, and transferring background processes to the front-end. Therefore, most processes killed on the local machine are also carried out in the shel environment. For this reason, the system engineers may still use the kill command to kill shell Sub-processes.

[1] [2] [3] [4] Next page