Run pgrep nginx.
pgrep nginx
Mission 356
Process signal evidence
Identify a process, inspect the snapshot, and record a simulated signal.
Package/process opspgreppskill
Lesson 356 of 360
0/360 lessons
0/17 missions
Package/process ops · 8 minutes
New learnerrank
0XP
0%complete
learner@clairos:/home/learner $
Unix ops lab: type a command, press Enter
Instructions
8 minutes
Click any instruction for the command details, the why, and the common mistake to avoid.
Run ps.
ps
Run kill 42.
kill 42
Save progress
Keep learning across sessions.
Create a free account to sync completed lessons, XP, streaks, course status, and your next lesson across sessions.
Checking account status...
Progress sync is idle.
0XP
New learnerrank
0day streak
0best streak
0daily streak
0lessons
0courses
0missions
0tasks
Noverified
Progress sync stores completion IDs, scores, streaks, badges, and game settings. Terminal contents, editor snippets, lab scratch, email, and real names are never published on leaderboards or share cards.
Lesson support
What to notice while you play.
Build repeatable confidence with choosing a process signal from observable evidence.
Start with pgrep nginx, inspect the result, then continue in order.
Choosing a process signal from observable evidence helps operators explain what they know before they change anything.
- Skipping the output that proves choosing a process signal from observable evidence.
- Changing several things before recording a baseline.
Reference
Commands in this lesson.
ps
Show training server processes.