thomasabishop/eolas
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Last Sync: 2022-08-28 10:00:04

Browse source
This commit is contained in:
tactonbishop 2022-08-28 10:00:04 +01:00
parent 79475c2efb
commit 813a0eb326
1 changed files with 29 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

32
Programming_Languages/Shell_Scripting/Processes.md
View file

@ -17,6 +17,31 @@ The command in its most minimal application returns the following
7112 pts/2 00:00:00 ps
```
With the `-e` modifier we can list more processes:
```
PID TTY TIME CMD
1 ? 00:00:05 systemd
2 ? 00:00:00 kthreadd
3 ? 00:00:00 rcu_gp
4 ? 00:00:00 rcu_par_gp
5 ? 00:00:00 netns
7 ? 00:00:00 kworker/0:0H-events_highpri
9 ? 00:00:00 mm_percpu_wq
11 ? 00:00:00 rcu_tasks_kthread
12 ? 00:00:00 rcu_tasks_rude_kthread
13 ? 00:00:00 rcu_tasks_trace_kthread
14 ? 00:00:08 ksoftirqd/0
15 ? 00:03:20 rcu_preempt
16 ? 00:00:00 rcub/0
17 ? 00:00:00 migration/0
18 ? 00:00:00 idle_inject/0
20 ? 00:00:00 cpuhp/0
21 ? 00:00:00 cpuhp/1
22 ? 00:00:00 idle_inject/1
23 ? 00:00:00 migration/1
```
<dl>
<dt>pid</dt>
<dd>Process ID: every currently running process has a unique ID<dd>
@ -43,8 +68,9 @@ The command in its most minimal application returns the following
## Process termination
The general schema is: `kill [pid]`. This allows for process clean-up. If this doesn't succeed you can force with `KILL [pid]` which will terminate the process immediately but is obviously more risky.
The general schema is: `kill [pid]`. This allows for process clean-up. If this doesn't succeed you can force with `KILL [pid]` which will terminate the process immediately but is obviously more risky.
We can also start/stop processes with modifiers on `kill`:
* `kill -STOP pid`
* `kill -CONT pid`
- `kill -STOP pid`
- `kill -CONT pid`