Process Discovery and Termination
One objective covering both halves: finding CPU and memory-intensive processes and killing them. Real load is generated so the numbers are real, and a process that traps SIGTERM is used to show why kill sometimes appears to do nothing and what to do about it.
Operating Running Systems Guide 25 of 67 Beginner
- OSRHEL 10.0
- Kernel6.12.0-55.9.1.el10_0
- dnf4.20.0
- Flatpak1.16.0
- TimeAbout 14 min
ps accepts both BSD options (ps aux) and UNIX options (ps -ef). They are not interchangeable and mixing them silently changes the meaning - ps aux and ps -aux are different requests. Pick one style.
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| RHCSA-A01 | 192.168.0.31 | RHEL 10.0 | Practice node (graded) - spare /dev/sda | 2 Core | 4 GB | 50 GB + 15 GB |
This guide includes
Use this when something is consuming the machine and has to stop. This matters because finding the heaviest process needs the right sort key for each resource - and one signal cannot be refused.
- listing what is running, with the fields that actually matter
- finding the heaviest, sorting on the right thing for CPU and for memory
- generating real load, so the numbers mean something
- choosing a signal, including the one that cannot be refused
- finding processes by owner
Before you start
- A sudo-capable account.
- The session starts CPU-burning processes and kills them all, each with its own timeout as a safety net.
-
What is running
-
Finding the heaviest
-
Some load to find
-
Signals, and the one that cannot be refused
-
Finding processes by owner