Scheduling Tasks with Cron

Welcome to the world of automation! In this lesson, you'll learn about cron, a powerful utility in Linux that lets you schedule commands or scripts to run automatically at specific times.

Imagine setting up daily backups or hourly system checks without lifting a finger – that's cron's job!

Each user on a Linux system has their own crontab (cron table) file. This is where you store all your scheduled tasks.

To edit your personal crontab, you'll use the command crontab -e. This opens the file in your default text editor, ready for you to add new jobs.

A crontab entry consists of six parts. The first five define when your command will run, and they are separated by spaces:

• Minute: 0-59
• Hour: 0-23 (0 is midnight)
• Day of Month: 1-31
• Month: 1-12 (or Jan-Dec)
• Day of Week: 0-7 (0 or 7 is Sunday, 1 is Monday)

The sixth and final part of a crontab entry is the command or script you want to execute.

It's crucial to use absolute paths for commands and scripts here (e.g., /usr/bin/python instead of just python). Cron jobs run in a minimal environment, so your usual PATH might not be available.

To make your schedules flexible, cron uses special characters:

• * (asterisk): Matches all possible values (e.g., every minute, every hour).
• , (comma): Separates a list of values (e.g., 1,15 for minutes 1 and 15).
• - (hyphen): Defines a range of values (e.g., 9-17 for hours 9 through 17).
• / (slash): Specifies step values (e.g., */10 for every 10 minutes).

For common scheduling needs, cron offers convenient shortcuts that replace the first five time fields:

• @reboot: Runs once after system reboot.
• @yearly (or @annually): Runs once a year (0 0 1 1 *).
• @monthly: Runs once a month (0 0 1 * *).
• @weekly: Runs once a week (0 0 * * 0).
• @daily (or @midnight): Runs once a day (0 0 * * *).
• @hourly: Runs once an hour (0 * * * *).

Let's create a simple script that logs a greeting, then schedule it to run every day at 10:00 AM.

1. Create the script (e.g., ~/greet.sh):
2. Make it executable: chmod +x ~/greet.sh
3. Add to crontab (crontab -e):
   0 10 * * * /home/user/greet.sh
   This entry means: At minute 0, hour 10 (10 AM), every day of the month, every month, every day of the week, run /home/user/greet.sh.

Once you've added cron jobs, you'll need to manage them:

• To list your current crontab entries: crontab -l
• To remove all your crontab entries (use with extreme caution, as there's no undo!): crontab -r

Always review your crontab with crontab -l after making changes to ensure your entries are correct.

Remember that cron jobs run in a minimal environment. This means they often don't have the same environment variables (like PATH) as your interactive shell.

If your script relies on specific commands, use their absolute paths or define necessary environment variables directly within your crontab file at the top, like PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin.

You need to schedule a script named /home/user/daily_report.sh to run at 9:15 AM every weekday (Monday to Friday). Which crontab entry is correct?

Great job! You've now mastered the fundamentals of cron for scheduling tasks.

• You learned about the crontab file and how to edit it with crontab -e.
• You understand the six fields of a cron entry, including time fields and the command.
• You explored special characters and predefined shortcuts for flexible scheduling.
• You know how to manage your jobs with crontab -l and crontab -r.
• You also learned about the importance of absolute paths and environment variables in cron's context.

Now go forth and automate!