Skip to content

08-process.md #1926

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 13, 2024
Merged

08-process.md #1926

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 9 additions & 9 deletions docs/books/admin_guide/08-process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -399,7 +399,7 @@ Examples:

!!! note

Before you kill a process, it's best to know exactly what the process is for, otherwise it can lead to system crashes or other unpredictable problems.
Before you kill a process, it's best to know exactly what it is for; otherwise, it can lead to system crashes or other unpredictable problems.

In addition to sending signals to the relevant processes, the `pkill` command can also end the user's connection session according to the terminal number, such as:

Expand All @@ -409,12 +409,12 @@ $ pkill -t pts/1

### `killall` command

The function of this command is roughly the same as that of the `pkill` command. The usage is - `killall [option] [ -s SIGNAL | -SIGNAL ] NAME`. The default signal is _SIGTERM_.
This command's function is roughly the same as that of the `pkill` command. The usage is —`killall [option] [ -s SIGNAL | -SIGNAL ] NAME`. The default signal is _SIGTERM_.

| Options | Description |
| :--- | :--- |
| `-l` | list all known signal names |
| `-i` | ask for confirmation before killing |
| `-l` | lists all known signal names |
| `-i` | asks for confirmation before killing |
| `-I` | case insensitive process name match |

Example:
Expand All @@ -430,9 +430,9 @@ This command displays the progress in a tree style, and its usage is - `pstree [
| Option | Description |
| :--- | :--- |
| `-p` | Displays the PID of the process |
| `-n` | sort output by PID |
| `-h` | highlight current process and its ancestors |
| `-u` | show uid transitions |
| `-n` | sorts output by PID |
| `-h` | highlights the current process and its ancestors |
| `-u` | shows uid transitions |

```bash
$ pstree -pnhu
Expand Down Expand Up @@ -467,10 +467,10 @@ systemd(1)─┬─systemd-journal(595)

Hazard:

* Occupying system resources and causing a decrease in machine performance.
* They are occupying system resources and causing a decrease in machine performance.
* Unable to generate new child processes.

How to check if there are any zombie processes in the current system?
How can we check for any zombie processes in the current system?

```
$ ps -lef | awk '{print $2}' | grep Z
Expand Down