Server operations · Lesson 16 of 36 · 8 minutes

Top process view

Read a simulated top snapshot before deeper process checks.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Show top snapshot
Run top.
Hint & worked example
Inspect a single training snapshot of process and resource activity.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
top
```
Remember: This lab does not run a continuously refreshing process monitor.
2
Show process list
Run ps.
Hint & worked example
Inspect a bounded snapshot of simulated processes.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
ps
```
Remember: A process being present does not prove that its service can handle requests.
3
Find nginx pids
Run pgrep nginx.
Hint & worked example
Find simulated process IDs by a name pattern.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
pgrep nginx
```
Remember: Verify a process identity before sending a signal.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

top: Inspect a single training snapshot of process and resource activity.
This lab does not run a continuously refreshing process monitor.
ps: Inspect a bounded snapshot of simulated processes.
A process being present does not prove that its service can handle requests.
pgrep: Find simulated process IDs by a name pattern.
Verify a process identity before sending a signal.

Worked example and expected result

$ top

top - 10:26:04 up 12 days, 1 learner, load average: 0.04, 0.03, 0.01
PID USER      %CPU %MEM COMMAND
42  www-data   0.2  1.1 nginx
77  root       0.1  0.8 sshd
126 root       0.0  0.3 cron

Exit status: 0. The command completed successfully in the training fixture.

$ ps

PID  USER      COMMAND
1    root      systemd --simulated
42   www-data  nginx: static process
77   root      sshd: listener
108  learner   clairos-learn-terminal
126  root      cron

Exit status: 0. The command completed successfully in the training fixture.

$ pgrep nginx

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Repeat this workflow in the sandbox with a different scratch filename. Keep the system fixtures unchanged and compare the observed output with your expectation before moving on.

Explain it

In “Top process view”, which interpretation is safe?A successful first check guarantees that every dependent service is healthy.A process being present does not prove that its service can handle requests.A command appearing in history proves it completed successfully.

Apply it elsewhere

Before adapting the ps workflow from “Top process view” to another server, what should you do?Confirm the current directory, target identity, permissions, and the installed command behavior first.Paste the training paths unchanged into production.Skip output inspection whenever the command is familiar.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Signal simulation Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

GNU Coreutils manual · GNU Bash manual