Package/process ops · Lesson 15 of 20 · 8 minutes

Signal choice review

Record signal intent without stopping anything.

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
Find nginx pid
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.
2
Record signal
Run kill 42.
Hint & worked example
Send an allowlisted signal to a simulated process target.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
kill 42
```
Remember: Prefer the service manager for managed daemons and understand the signal before using it.
3
Read nginx journal
Run journalctl -u nginx -n 2.
Hint & worked example
Read the training journal by unit or a bounded line window.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
journalctl -u nginx -n 2
```
Remember: A relevant unit and time range are more useful than an unfiltered wall of logs.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

pgrep: Find simulated process IDs by a name pattern.
Verify a process identity before sending a signal.
kill: Send an allowlisted signal to a simulated process target.
Prefer the service manager for managed daemons and understand the signal before using it.
journalctl: Read the training journal by unit or a bounded line window.
A relevant unit and time range are more useful than an unfiltered wall of logs.

Worked example and expected result

$ pgrep nginx

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

$ kill 42

signal recorded for simulated PID 42; no process was stopped.

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

$ journalctl -u nginx -n 2

May 26 08:10:01 clairos-learn nginx[42]: started static training site
May 26 08:20:05 clairos-learn nginx[42]: access denied for /api/test by static rule

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 “Signal choice review”, which interpretation is safe?A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.Prefer the service manager for managed daemons and understand the signal before using it.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Top ps snapshot 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