Editing crontab (crontab -e) in Linux CLI - Step-by-Step Execution

Concept Flow - Editing crontab (crontab -e)

User runs 'crontab -e'

↓

System opens crontab file in editor

↓

User edits or adds cron jobs

↓

User saves and exits editor

↓

System installs new crontab

↓

Cron daemon schedules tasks

↓

Tasks run at scheduled times

The user opens the crontab file with 'crontab -e', edits or adds scheduled tasks, saves and exits, then the system updates the schedule.

Execution Sample

Linux CLI

crontab -e
# Edit the file to add:
0 7 * * * /home/user/backup.sh
# Save and exit

This opens the crontab editor, adds a job to run backup.sh every day at 7:00 AM, then saves the changes.

Execution Table

Step	Action	System Response	User Input	Result
1	Run 'crontab -e'	Opens crontab file in default editor	N/A	Crontab file ready for editing
2	User adds line '0 7 * * * /home/user/backup.sh'	File content updated	Add cron job line	New job scheduled
3	User saves and exits editor	System reads updated file	Save and exit	Crontab updated
4	System installs new crontab	Cron daemon reloads schedule	N/A	New job active
5	Cron daemon runs job at 7:00 AM	Executes /home/user/backup.sh	N/A	Backup script runs
6	User runs 'crontab -l' to list jobs	Displays current cron jobs	N/A	Shows new job in list
7	User exits	No further action	N/A	Session ends

💡 User finishes editing and saves, system installs new crontab, then cron daemon schedules tasks accordingly

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
crontab file content	Empty or previous jobs	Added '0 7 * * * /home/user/backup.sh'	Saved updated content	Updated crontab with new job
cron daemon schedule	Old schedule	No change yet	Reloads new schedule	Schedules new job daily at 7:00 AM

Key Moments - 3 Insights

Why doesn't the new cron job run immediately after editing?

Because the cron daemon only reads the updated crontab after you save and exit the editor, as shown in steps 3 and 4 in the execution table.

What happens if you forget to save before exiting the editor?

The system will not install the new crontab, so your changes are lost. The execution table step 3 shows saving is required to update the schedule.

How can you verify your new cron job was added?

By running 'crontab -l' which lists current cron jobs, as shown in step 6 of the execution table.

Visual Quiz - 3 Questions

Look at the execution table, what happens at step 4?

A Cron daemon runs the scheduled job

B User edits the crontab file

C System installs the new crontab and cron daemon reloads schedule

D User lists current cron jobs

💡 Hint

Check the 'System Response' and 'Result' columns at step 4 in the execution table

At which step does the user save and exit the editor?

A Step 3

B Step 2

C Step 1

D Step 5

💡 Hint

Look for 'User saves and exits editor' in the 'Action' column of the execution table

If the user forgets to save the file, what will the cron daemon schedule?

A The new job will be scheduled anyway

B The old schedule remains unchanged

C The cron daemon will show an error

D The cron daemon will delete all jobs

💡 Hint

Refer to the key moment about saving changes and step 3 in the execution table

Concept Snapshot

Editing crontab with 'crontab -e':
- Opens your crontab file in an editor
- Add or change scheduled jobs (one per line)
- Save and exit to install changes
- Cron daemon reloads and runs jobs on schedule
- Use 'crontab -l' to list jobs
- Unsaved changes are lost

Full Transcript

When you run 'crontab -e', the system opens your crontab file in a text editor. You can add or edit scheduled tasks by writing lines with timing and commands. After editing, you must save and exit the editor. The system then installs the new crontab, and the cron daemon reloads the schedule to run your tasks at the specified times. You can check your current cron jobs anytime with 'crontab -l'. Remember, if you do not save before exiting, your changes will not be applied.