Bird
0
0

After editing crontab with crontab -e, your job does not run. Which of these is a likely cause?

medium📝 Debug Q7 of 15
Linux CLI - Cron and Scheduling
After editing crontab with crontab -e, your job does not run. Which of these is a likely cause?
AThe cron daemon is not installed
BYou forgot to save and exit the editor
CYou used an invalid command path
DYou scheduled the job for a past date
Step-by-Step Solution
Solution:

  1. Step 1: Confirm saving changes

    If you do not save and exit the editor, changes are not applied.

  2. Step 2: Understand cron behavior

    Cron jobs run only if saved properly; invalid paths or daemon issues cause different errors.

  3. Final Answer:

    You forgot to save and exit the editor -> Option B

  4. Quick Check:

    Unsaved edits mean no cron job update [OK]
Quick Trick: Always save and exit editor to apply cron changes [OK]
Common Mistakes:
  • Assuming cron runs jobs without saving
  • Confusing scheduling with command errors

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Linux CLI Quizzes
Archiving and Compression - tar (create and extract archives) - Quiz 2easy Archiving and Compression - tar with compression (-z, -j, -J) - Quiz 1easy Environment and Configuration - History command and search - Quiz 12easy Environment and Configuration - Aliases for shortcuts - Quiz 12easy Package Management - Installing, updating, removing packages - Quiz 8hard SSH and Remote Access - tmux for persistent sessions - Quiz 6medium SSH and Remote Access - SCP for file transfer - Quiz 5medium SSH and Remote Access - SCP for file transfer - Quiz 3easy System Administration - System resource monitoring (free, uptime, vmstat) - Quiz 6medium System Administration - Startup and init systems (systemd) - Quiz 7medium