CertGrid CertGrid
Hands-on Lab·Linux Foundation Certified System Administrator

Processes, signals and what is using the CPU

Finding the process, understanding what state it is in, and stopping it without breaking anything else. ps has two completely different option styles that produce the same processes, kill sends a signal rather than killing, and nice numbers run backwards from priority. All three cost marks.

Operations Deployment Guide 16 of 38 Intermediate

procps-ng on both families; ps, kill, nice and renice are identical. systemd-run needs systemd, which both have.

Both families. The RHEL transcript came first, during an outage that took both Ubuntu hosts offline; the Ubuntu half was captured afterwards and is the last step of each page, because Ubuntu is what LFCS is most likely to sit you in front of.
Server NameIP AddressOSRolesCPURAMHDD
LFCS-A01192.168.0.70Ubuntu 26.04 LTSPrimary host - most guides run only here2 Core4 GB50 GB
LFCS-C01192.168.0.72AlmaLinux 10.2The other distribution - dnf, firewalld and NetworkManager2 Core4 GB50 GB

This guide includes

Use this for finding and stopping the process you were asked about. This matters because niceness runs backwards from priority - and two signals cannot be caught at all.

Before you start

  1. ps, in its two incompatible styles

  2. The state column, which is the diagnosis

  3. The tree, and who started what

  4. Finding the one you want

  5. What is using the CPU and the memory

  6. Signals, and the two that cannot be caught

  7. Niceness runs backwards from priority

  8. And a process that outlives your session

  9. The same process tools on Ubuntu

Official sources