Why cron automates recurring tasks in Linux CLI - See It in Action

Why cron automates recurring tasks

📖 Scenario: You are managing a small server that needs to perform regular backups every day. Doing this manually is tiring and easy to forget. You want to use a tool that runs commands automatically at set times.

🎯 Goal: Learn how to use cron to automate a simple recurring task that runs every minute for demonstration. You will create a cron job that writes the current date and time to a file repeatedly.

📋 What You'll Learn

Create a text file to store output

Write a cron job command that runs every minute

Use the correct cron syntax for timing

Verify the cron job runs and appends output

💡 Why This Matters

🌍 Real World

Automating tasks like backups, system updates, or report generation saves time and avoids forgetting important jobs.

💼 Career

System administrators and developers use cron to schedule scripts and commands to run automatically, improving efficiency and reliability.

1

DATA SETUP: Create a file to store output

Create an empty file called /tmp/cron_test.log using the touch command.

Linux CLI

# Use touch to create /tmp/cron_test.log
# Your code here

Hint

Use touch to create an empty file if it does not exist.

2

CONFIGURATION: Write the cron job command

Write a cron job line that runs every minute and appends the current date and time to /tmp/cron_test.log. Use the command date >> /tmp/cron_test.log.

Linux CLI

touch /tmp/cron_test.log
# Write the cron job line below
# Your code here

Hint

The cron timing * * * * * means every minute.

3

CORE LOGIC: Add the cron job to the crontab

Add the cron job line * * * * * date >> /tmp/cron_test.log to your user crontab using crontab -l | { cat; echo "* * * * * date >> /tmp/cron_test.log"; } | crontab -.

Linux CLI

touch /tmp/cron_test.log
* * * * * date >> /tmp/cron_test.log
# Add the cron job to crontab below
# Your code here

Hint

This command appends the new cron job to your existing crontab.

4

OUTPUT: Check the output file for new entries

Use tail -n 3 /tmp/cron_test.log to display the last three lines of the file and verify the cron job is running.

Linux CLI

touch /tmp/cron_test.log
* * * * * date >> /tmp/cron_test.log
crontab -l | { cat; echo "* * * * * date >> /tmp/cron_test.log"; } | crontab -
# Check the last 3 lines of /tmp/cron_test.log
# Your code here

Hint

The output should show recent date and time entries, one per minute.

Practice

1. Why do people use cron to automate tasks on Linux systems?

easy

A. To run tasks automatically at set times without manual effort

B. To speed up the computer's hardware components

C. To create graphical user interfaces for applications

D. To permanently delete files from the system

Solution

1. Step 1: Understand the purpose of cron

   cron is a tool that schedules tasks to run automatically at specified times.

2. Step 2: Identify the benefit of automation

   Automating tasks saves time and prevents forgetting to run important jobs manually.

3. Final Answer:

   To run tasks automatically at set times without manual effort -> Option A

4. Quick Check:

   Cron automates tasks = To run tasks automatically at set times without manual effort [OK]

Hint: Cron runs tasks on schedule to save time and effort [OK]

Common Mistakes:

• Thinking cron speeds up hardware
• Confusing cron with GUI tools
• Believing cron deletes files permanently

2. Which of the following is the correct syntax for a cron schedule line to run a task every day at 3 AM?

easy

A. 3 0 * * * /path/to/script.sh

B. 0 3 * * * /path/to/script.sh

C. * 3 * * * /path/to/script.sh

D. 0 0 3 * * /path/to/script.sh

Solution

1. Step 1: Understand cron time fields

   The five fields are: minute, hour, day of month, month, day of week.

2. Step 2: Match 3 AM daily schedule

   Minute = 0, Hour = 3, and all other fields as * to mean every day.

3. Final Answer:

   0 3 * * * /path/to/script.sh -> Option B

4. Quick Check:

   Minute=0, Hour=3 daily = 0 3 * * * /path/to/script.sh [OK]

Hint: Minute first, then hour; 3 AM is hour 3, minute 0 [OK]

Common Mistakes:

• Swapping hour and minute fields
• Using * for minute instead of 0
• Misplacing day or month fields

3. Given this cron entry: 30 2 * * 1 /usr/bin/backup.sh, what does it do?

medium

A. Runs backup.sh every hour at 2:30

B. Runs backup.sh every day at 2:30 AM

C. Runs backup.sh every Monday at 2:30 AM

D. Runs backup.sh every minute on Mondays

Solution

1. Step 1: Decode the cron time fields

   30 = minute, 2 = hour, * = every day/month, 1 = Monday (day of week).

2. Step 2: Interpret the schedule

   The command runs at 2:30 AM only on Mondays.

3. Final Answer:

   Runs backup.sh every Monday at 2:30 AM -> Option C

4. Quick Check:

   Minute=30, Hour=2, Day=Monday = Runs backup.sh every Monday at 2:30 AM [OK]

Hint: Day of week 1 means Monday; time is hour then minute [OK]

Common Mistakes:

• Assuming it runs daily instead of weekly
• Mixing up day of week with day of month
• Confusing minute and hour positions

4. A user writes this cron line: 60 24 * * * /home/user/script.sh. What is wrong?

medium

A. Minute value 60 is invalid; should be 0-59

B. Nothing is wrong; it will run daily at midnight

C. Hour value 24 is invalid; should be 0-23

D. Both minute and hour values are invalid

Solution

1. Step 1: Check minute field validity

   Minute must be between 0 and 59; 60 is invalid.

2. Step 2: Check hour field validity

   Hour must be between 0 and 23; 24 is invalid.

3. Final Answer:

   Both minute and hour values are invalid -> Option D

4. Quick Check:

   Minute=60 and Hour=24 invalid = Both minute and hour values are invalid [OK]

Hint: Minutes 0-59, hours 0-23 only [OK]

Common Mistakes:

• Thinking 60 minutes means next hour
• Assuming 24 is valid hour for midnight
• Ignoring cron field limits

5. You want to automate a cleanup script to run every 15 minutes using cron. Which cron schedule line is correct?

hard

A. */15 * * * * /usr/local/bin/cleanup.sh

B. 15 * * * * /usr/local/bin/cleanup.sh

C. 0,15,30 * * * * /usr/local/bin/cleanup.sh

D. 0-15 * * * * /usr/local/bin/cleanup.sh

Solution

1. Step 1: Understand the syntax for every 15 minutes

   The */15 in the minute field means every 15 minutes.

2. Step 2: Compare options

   */15 * * * * /usr/local/bin/cleanup.sh uses */15, which is the standard way to run every 15 minutes. 0,15,30 * * * * /usr/local/bin/cleanup.sh lists minutes explicitly but misses 45. 15 * * * * /usr/local/bin/cleanup.sh runs only at minute 15 each hour. 0-15 * * * * /usr/local/bin/cleanup.sh runs minutes 0 to 15 every hour, not every 15 minutes.

3. Final Answer:

   */15 * * * * /usr/local/bin/cleanup.sh -> Option A

4. Quick Check:

   Every 15 minutes = */15 in minute field [OK]

Hint: Use */15 in minute field for every 15 minutes [OK]

Common Mistakes:

• Using single minute value instead of interval
• Listing minutes but missing some intervals
• Using range instead of step syntax