Run crontab -l.
crontab -l
Mission 339
Scheduled service evidence
Relate a user schedule to cron service state and log entries.
Server operationscrontabsystemctlgrep
Lesson 339 of 360
0/360 lessons
0/17 missions
Server operations · 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 systemctl status cron.
systemctl status cron
Run grep CRON /var/log/cron.log.
grep CRON /var/log/cron.log
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 triangulating scheduled work from configuration and runtime evidence.
Start with crontab -l, inspect the result, then continue in order.
Triangulating scheduled work from configuration and runtime evidence helps operators explain what they know before they change anything.
- Skipping the output that proves triangulating scheduled work from configuration and runtime evidence.
- Changing several things before recording a baseline.
Reference
Commands in this lesson.
grep [-i] <text> <file>
Find literal text inside a file.
systemctl status <service>
Inspect simulated service status.
crontab -l
List a simulated learner crontab.