Why cron automates recurring tasks in Linux CLI - Quick Recap

Recall & Review

beginner

What is the main purpose of cron in Linux?

Cron is a tool that automatically runs tasks at scheduled times or intervals without manual intervention.

beginner

How does cron help with recurring tasks?

Cron runs commands or scripts repeatedly at fixed times, like every day or every hour, so you don't have to remember to run them yourself.

beginner

What file does cron use to schedule tasks?

Cron uses a file called a crontab where you list commands and the times they should run.

beginner

Why is automating recurring tasks with cron useful in real life?

It saves time and avoids mistakes by running important jobs like backups or updates automatically, even when you forget or are away.

beginner

Can cron run tasks when the computer is off?

No, cron only runs tasks when the computer is on and the cron service is running.

What does cron automate?

A Graphical user interface actions

B One-time manual commands

C Recurring tasks at scheduled times

D Hardware device drivers

Cron automates tasks that need to run repeatedly at set times.

Where do you list tasks for cron to run?

A /etc/passwd

B crontab file

C /var/log/syslog

D /home/user/.bashrc

The crontab file contains the schedule and commands for cron.

Which of these is a benefit of using cron?

A Automatic task running

B Forgetting to run tasks

C Slowing down the computer

D Manual task execution

Cron automatically runs tasks, saving time and reducing errors.

If the computer is off, what happens to cron jobs?

A They run twice

B They run when the computer turns on

C They run anyway

D They do not run

Cron jobs only run when the computer and cron service are active.

Which command shows your current cron jobs?

A crontab -l

B cron -show

C ls /cron

D cronjobs --list

The command 'crontab -l' lists your scheduled cron jobs.

Explain in your own words why cron is useful for automating recurring tasks.

Think about tasks you do often and how cron can help run them without you.

Describe how you would set up a simple cron job to run a backup script every day at 2 AM.

Remember the crontab time fields and the command to run your script.

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