LAB-PROC-01 - The Process Lifecycle
Inspect running processes, identify PIDs, and connect a few basic commands to the process model without needing advanced process theory yet.
The Process Lifecycle
Inspect running processes, identify PIDs, and connect a few basic commands to the process model without needing advanced process theory yet.
- Inspect running processes, identify PIDs, and connect a few basic commands to the process model without needing advanced process theory yet.
- Repeat the workflow without copy-paste or step-by-step prompting.
- Double-check process IDs and commands before stopping anything outside the lab scenario.
Part A: The Field Guide
Processes become easier to understand once you stop treating them as invisible background magic.
This lab keeps the goal simple:
- list what is running
- find a PID
- observe a child process
- connect the command output to the mental model
Safe Default
In this lab, observe first. You do not need to kill anything to understand what a process is.
Part B: The Drill Deck
Terminal required: this lab is mostly observational.
G Guided Step by step - type exactly this and compare the result >
Exercise G1: Look at your current shell context
- Run
ps - Notice that you usually see your current shell and the
pscommand itself - Identify the PID column
- Identify the command names shown
Exercise G2: Take a wider snapshot
- Run
ps aux | head -n 10 - Notice that the list includes many more processes than the simple
psoutput - Find one line and identify the user, PID, and command fields
Exercise G3: Create one easy target
- Run
sleep 120 & - Run
jobs - Run
pgrep sleep - Run
ps aux | grep sleep - Notice that different tools help in different ways
S Solo Task described, hints available - figure it out >
Exercise S1: Parent and child reasoning
- Start from your shell process shown in
ps - Run a short command such as
sleep 5 - Explain how your shell acts as the parent for the command it launched
Exercise S2: Optional tree view
If pstree is available:
- run
pstree - look for your shell in the hierarchy
- explain what the tree is showing in simple terms
M Mission Real scenario - no hints, combine multiple skills >
Mission M1: Find by name, then verify by snapshot
Create one easy background target such as sleep 180 &, then:
- find it with
pgrep - verify it in
ps aux - explain why names alone can be ambiguous when multiple similar processes exist
If you can move between those views calmly, the process model is becoming usable.
What to do next
Best next step LearningReturn to the related lesson if you want the concept explained more deeply.