Run journalctl -u nginx -n 4.
journalctl -u nginx -n 4
Mission 321
Journal line numbering
Number a narrowed service journal so evidence is easy to reference.
Text and logsjournalctlnl
Lesson 321 of 360
0/360 lessons
0/17 missions
Text and logs · 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 journalctl -u nginx -n 4 | nl.
journalctl -u nginx -n 4 | nl
Run systemctl status nginx.
systemctl status nginx
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 narrowing and numbering service journal output.
Start with journalctl -u nginx -n 4, inspect the result, then continue in order.
Narrowing and numbering service journal output helps operators explain what they know before they change anything.
- Skipping the output that proves narrowing and numbering service journal output.
- Changing several things before recording a baseline.
Reference
Commands in this lesson.
nl [file]
Number lines from a file or supported text pipeline.
journalctl -u <service>
Read simulated service journal entries.