A beginner-friendly guide to understanding Cron, Crontab, and Linux task scheduling through hands-on practice.
Introduction
As part of my DevOps and Linux learning journey, I recently explored Cron and Crontab, two powerful tools used to automate repetitive tasks in Linux systems.
At first, the cron syntax looked intimidating:
I had no idea what all those asterisks meant.
However, after understanding the basics and performing some hands-on exercises, I realized that Cron is one of the most useful tools for Linux administrators, DevOps engineers, and backend developers.
In this blog, I'll share what I learned about Cron and Crontab, how I created my first cron job, common scheduling expressions, troubleshooting tips, and how cron is used in real-world applications.
What is Cron?
Cron is a Linux utility/service that allows users to automate tasks by scheduling commands or scripts to run at specific times.
Instead of manually executing commands every day, every hour, or every week, Cron can do it automatically.
Real-World Use Cases
Cron is commonly used for:
Database backups
Log file cleanup
Monitoring server health
Sending automated emails
Running reports
Data synchronization
System maintenance tasks
How Cron Works
User
│
▼
Crontab File
│
▼
Cron Service (crond)
│
▼
Execute Scheduled Commands
The Cron service continuously checks the scheduling rules stored in the Crontab file and executes commands when their scheduled time arrives.
What is Crontab?
Crontab stands for Cron Table.
It is a configuration file that contains information about:
When a task should run
Which command or script should run
Think of Crontab as a timetable for the Cron service.
Common Crontab Commands
List current cron jobs:
crontab -l
Edit cron jobs:
crontab -e
Remove all cron jobs:
crontab -r
After adding or modifying cron jobs, Cron automatically picks up the changes.
Understanding Cron Syntax
A cron job follows this format:
- * * * * command_to_execute
Each asterisk represents a specific time field.
- * * * * command
Field Breakdown
Field Allowed Values
Minute 0–59
Hour 0–23
Day of Month 1–31
Month 1–12
Day of Week 0–7
My Notes While Learning Cron
While studying Cron, I made the following notes:
Cron
Linux utility/service
Allows automation of tasks
Executes commands at scheduled intervals
Crontab
Stores scheduling information
Contains execution details for commands/scripts
Useful Commands
crontab -l
Lists active cron jobs.
crontab -e
Opens cron editor.
crontab -r
Removes existing cron jobs.
My First Cron Job (Hands-On)
To understand how Cron actually works, I created my first cron job.
Objective
Write the current date and time to a log file every minute.
Step 1: Create a Shell Script
Create a script file:
nano test.sh
Add the following code:
!/bin/bash
date >> /tmp/cron.log
Save the file.
Step 2: Make the Script Executable
chmod +x test.sh
Verify permissions:
ls -l test.sh
Output:
-rwxr-xr-x 1 user user 35 Jun 12 10:15 test.sh
Step 3: Open Crontab Editor
crontab -e
If this is your first time using crontab, Linux may ask you to select an editor.
Choose Nano if you're a beginner.
Step 4: Add a Cron Job
Add the following line:
- * * * * /home/user/test.sh
Explanation:
Symbol Meaning
- Every minute
- Every hour
- Every day
- Every month
- Every day of week
This means:
Execute test.sh every minute.
Save and exit.
Step 5: Verify Cron Job
Check if the cron job was saved.
crontab -l
Output:
- * * * * /home/user/test.sh Step 6: Wait One Minute
After one minute, check the log file.
cat /tmp/cron.log
Example Output:
Thu Jun 12 10:20:01 IST 2026
Thu Jun 12 10:21:01 IST 2026
Thu Jun 12 10:22:01 IST 2026
Success! 🎉
The cron job is running automatically every minute.
Common Cron Scheduling Examples
Every Minute
Every 5 Minutes
*/5 * * * *
Every 30 Minutes
*/30 * * * *
Every Hour
0 * * * *
Every Day at Midnight
0 0 * * *
Every Day at 9 AM
0 9 * * *
Every Sunday
0 0 * * 0
Every Monday at 9 AM
0 9 * * 1
Troubleshooting Issues I Learned About
When working with cron jobs, several issues can prevent them from running.
- Cron Service Not Running
Check status:
systemctl status crond
Start service:
sudo systemctl start crond
Enable on boot:
sudo systemctl enable crond
- Script Doesn't Have Execute Permission
Wrong:
-rw-r--r--
Correct:
-rwxr-xr-x
Fix:
chmod +x script.sh
- Wrong File Path
Cron often fails because relative paths are used.
Wrong:
./test.sh
Correct:
/home/darshan/test.sh
Always use absolute paths.
- Checking Cron Logs
Ubuntu:
grep CRON /var/log/syslog
CentOS/RHEL:
journalctl -u crond
These logs help identify execution issues.
Cron in Backend Development
While learning Node.js, I discovered that cron jobs are widely used in backend applications.
A popular package is:
npm install node-cron
Example:
import cron from "node-cron";
cron.schedule("* * * * *", () => {
console.log("Running every minute");
});
Common Backend Uses
Sending reminder emails
Cleaning expired sessions
Generating reports
Database backups
Scheduled notifications
Data synchronization
What I Learned
After learning Cron and Crontab, I gained a better understanding of Linux automation.
My key takeaways were:
✅ Cron is a Linux scheduling service.
✅ Crontab stores scheduling instructions.
✅ Cron expressions define execution timing.
✅ Always use absolute paths in cron jobs.
✅ Logs are essential for troubleshooting.
✅ Cron is heavily used in DevOps and backend systems.
Conclusion
Cron may seem confusing initially because of its scheduling syntax, but once you understand the structure and create your first cron job, it becomes a powerful automation tool.
Learning Cron helped me understand how Linux systems automate repetitive tasks without manual intervention. Whether you're a Linux beginner, aspiring DevOps engineer, system administrator, or backend developer, Cron is a skill worth learning.
This hands-on exercise of creating my first cron job gave me practical experience with Linux task scheduling and showed me how simple automation can save time and reduce manual work.