From 1fe3ca93e19c37192ada65d13baf33ae75c3b482 Mon Sep 17 00:00:00 2001 From: Ganna Zhyrnova <112796922+gannazhyrnova@users.noreply.github.com> Date: Mon, 4 Mar 2024 21:46:37 +0200 Subject: [PATCH] Update 08-process.md Grammar check --- docs/books/admin_guide/08-process.md | 50 ++++++++++++++-------------- 1 file changed, 25 insertions(+), 25 deletions(-) diff --git a/docs/books/admin_guide/08-process.md b/docs/books/admin_guide/08-process.md index c51349a0d8..7fe971db70 100644 --- a/docs/books/admin_guide/08-process.md +++ b/docs/books/admin_guide/08-process.md @@ -4,7 +4,7 @@ title: Process Management # Process Management -In this chapter you will learn how to work with processes. +In this chapter, you will learn how to work with processes. **** @@ -25,9 +25,9 @@ In this chapter you will learn how to work with processes. ## Generalities -An operating system consists of processes. These processes are executed in a specific order and are related to each other. There are two categories of processes, those focused on the user environment and those focused on the hardware environment. +An operating system consists of processes. These processes are executed in a specific order and are related. There are two categories of processes, those focused on the user environment and those focused on the hardware environment. -When a program runs, the system will create a process by placing the program data and code in memory and creating a **runtime stack**. A process is therefore an instance of a program with an associated processor environment (ordinal counter, registers, etc...) and memory environment. +When a program runs, the system will create a process by placing the program data and code in memory and creating a **runtime stack**. A process is an instance of a program with an associated processor environment (ordinal counter, registers, etc...) and memory environment. Each process has: @@ -36,10 +36,10 @@ Each process has: By successive filiations, the `init` process is the father of all processes. -* A process is always created by a parent process +* A parent process always creates a process * A parent process can have multiple child processes -There is a parent/child relationship between processes. A child process is the result of the parent process calling the _fork()_ primitive and duplicating its own code to create a child. The _PID_ of the child is returned to the parent process so that it can talk to it. Each child has its parent's identifier, the _PPID_. +There is a parent/child relationship between processes. A child process results from the parent calling the _fork()_ primitive and duplicating its code to create a child. The _PID_ of the child is returned to the parent process so that it can talk to it. Each child has its parent's identifier, the _PPID_. The _PID_ number represents the process at the time of execution. When the process finishes, the number is available again for another process. Running the same command several times will produce a different _PID_ each time. @@ -47,7 +47,7 @@ The _PID_ number represents the process at the time of execution. When the proce !!! Note - Processes are not to be confused with _threads_. Each process has its own memory context (resources and address space), while _threads_ from the same process share this same context. + Processes are not to be confused with _threads_. Each process has its memory context (resources and address space), while _threads_ from the same process share this context. ## Viewing processes @@ -77,12 +77,12 @@ Some additional options: | `-H` | Displays the information in a tree structure. | | `-I` | Displays additional information. | | `--sort COL` | Sort the result according to a column. | -| `--headers` | Displays the header on each page of the terminal. | +| `--headers` | Displays the header on each terminal page. | | `--format "%a %b %c"` | Customize the output display format. | Without an option specified, the `ps` command only displays processes running from the current terminal. -The result is displayed in columns: +The result is displayed in the following columns: ``` # ps -ef @@ -101,7 +101,7 @@ root 1 0 0 Jan01 ? 00:00/03 /sbin/init | `TIME` | Processing duration. | | `CMD` | Command executed. | -The behaviour of the control can be fully customized: +The behavior of the control can be fully customized: ``` # ps -e --format "%P %p %c %n" --sort ppid --headers @@ -126,7 +126,7 @@ The user process: The system process (_daemon_): * is started by the system -* is not associated with any terminal, and is owned by a system user (often `root`) +* is not associated with any terminal and is owned by a system user (often `root`) * is loaded at boot time, resides in memory, and is waiting for a call * is usually identified by the letter `d` associated with the process name @@ -134,9 +134,9 @@ System processes are therefore called daemons (_**D**isk **A**nd **E**xecution * ## Permissions and rights -When a command is executed, the user's credentials are passed to the created process. +The user's credentials are passed to the created process when a command is executed. -By default, the actual `UID` and `GID` (of the process) are therefore identical to the **actual** `UID` and `GID` (the `UID` and `GID` of the user who executed the command). +By default, the process's actual `UID` and `GID` (of the process) are identical to the **actual** `UID` and `GID` (the `UID` and `GID` of the user who executed the command). When a `SUID` (and/or `SGID`) is set on a command, the actual `UID` (and/or `GID`) becomes that of the owner (and/or owner group) of the command and no longer that of the user or user group that issued the command. Effective and real **UIDs** are therefore **different**. @@ -146,7 +146,7 @@ Each time a file is accessed, the system checks the rights of the process accord A process cannot be run indefinitely, as this would be to the detriment of other running processes and would prevent multitasking. -The total processing time available is therefore divided into small ranges, and each process (with a priority) accesses the processor in a sequenced manner. The process will take several states during its life among the states: +Therefore, the total processing time available is divided into small ranges, and each process (with a priority) accesses the processor sequentially. The process will take several states during its life among the states: * ready: waiting for the availability of the process * in execution: accesses the processor @@ -161,13 +161,13 @@ The end-of-process sequencing is as follows: 2. Release of the used memory 3. Sending a signal to the parent and child processes -When a parent process dies, its children are said to be orphans. They are then adopted by the `init` process which will destroy them. +When a parent process dies, their children are said to be orphans. They are then adopted by the `init` process, which will destroy them. ### The priority of a process -The processor works in time sharing with each process occupying a quantity of processor time. +The processor works in time sharing, with each process occupying a quantity of processor time. -The processes are classified by priority whose value varies from **-20** (the highest priority) to **+19** (the lowest priority). +The processes are classified by priority, whose value varies from **-20** (the highest priority) to **+19** (the lowest priority). The default priority of a process is **0**. @@ -236,7 +236,7 @@ $ nohup myprogram.sh 0