Files
rootnode-academy/content/root/root-01-computing-linux-foundations/m05-processes/04-guided-exercise-signals.md
T
ced4568andClaude Sonnet 5 15b616274b feat(root01): author Computing & Linux Foundations, and the real 01->05 prerequisite chain
Adds all 6 ROOT 01 modules (how computers run software, the shell, filesystem navigation,
files & text, processes, users & permissions foundations), each with a real lesson,
demonstration/guided exercise, knowledge check where warranted, a hands-on Lab, and a
reflection — 35 activities, 29 new content files.

Adds 6 new hands-on Linux scenarios (linux-inspect-hardware, linux-shell-basics,
linux-filesystem-navigation, linux-files-and-text, linux-process-management,
linux-permissions-foundations) plus 2 MCQ scenarios, using the existing generic scenario/
validation engine (docs/ROOT_FOUNDATIONS_LAB_STRATEGY.md §1) — every one tested end-to-end via
the real scenario setup/validate API, including negative tests confirming they correctly FAIL
when not actually solved (e.g. the process-management scenario fails while the target process
is still running; the permissions scenario is tested against a real `su - labuser` denial).

Wires rootnode-linux-foundations-assessment (2 required + 4 random-draw scenarios) using the
existing Phase 3B assessment engine.

Adds a real, server-side ROOT 01->02->03->04->05 course prerequisite chain
(courses.prerequisites) — verified live on two students: one who completed ROOT 01 sees ROOT 02
unlock; a fresh student sees ROOT 02 correctly locked while 03/04/05 stay vacuously satisfied
(their own prerequisite courses are still empty). ROOT 06+ and the Capstone are unaffected.

Co-Authored-By: Claude Sonnet 5 <[email protected]>
2026-08-26 12:59:52 -05:00

1.2 KiB

Guided Exercise: Choosing the Right Signal

This is a paper exercise — commit to an answer before checking it in the Lab.

Your task

For each situation, decide: plain kill (SIGTERM) first, or is kill -9 (SIGKILL) actually justified?

  1. A normal web server process you want to shut down for a routine restart.
  2. A process that received SIGTERM two minutes ago and is still running, showing no signs of responding.
  3. A script you just started by mistake, that hasn't done anything harmful yet.

A worked shape to check yourself against

  1. Plain kill — give it the chance to shut down cleanly (close connections, flush data, etc).
  2. kill -9 is now justified — you already gave it the polite chance, and it didn't respond.
  3. Plain kill first, still — "just started" doesn't change the default; SIGKILL is a last resort, not a shortcut for convenience.

Instructor Notes

Facilitation: Item 3 sometimes trips students who reach for -9 out of impatience — worth reinforcing that SIGTERM-first is the discipline REGARDLESS of urgency, since a process that ignores SIGTERM is the actual signal that escalation is warranted.

Approximate timing: 8-10 minutes live discussion; 5 minutes self-paced.