Scheduled Tasks with Cron

Manual tasks on a server can be repetitive and prone to human error. Automation helps you save time and ensures tasks are performed consistently.

Imagine needing to back up a database every night or clean up old log files every week. Doing this manually is tedious and easy to forget.

This is where scheduling tools come in handy! They allow your server to perform tasks automatically at specific times or intervals, freeing you up for more important work.

Cron is a fundamental utility in Linux for scheduling tasks. It's like a personal assistant for your server, ensuring that commands or scripts run automatically in the background at predetermined times.

These scheduled tasks are called cron jobs. Each user on a system can have their own list of cron jobs, stored in a special file called a crontab.

To manage your personal cron jobs, you use the crontab command.

• To edit your crontab file, type: crontab -e
• To list your current cron jobs, type: crontab -l
• To remove all your cron jobs, type: crontab -r (Use with caution!)

When you run crontab -e, it will open your crontab in your default text editor, often nano or vi.

Each line in your crontab represents a single cron job and follows a specific pattern. It has five time fields, followed by the command to execute.

The format is:

• 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)

You don't always need exact numbers. Cron offers special characters for flexibility:

• * (Asterisk): Matches "every" possible value for that field. E.g., * in the minute field means "every minute".
• - (Hyphen): Specifies a range. E.g., 9-17 in the hour field means "hours 9 through 17".
• , (Comma): Specifies a list of values. E.g., Mon,Wed,Fri or 1,3,5 for days of the week.
• / (Slash): Specifies step values. E.g., */5 in the minute field means "every 5 minutes".

Let's look at some common examples to solidify your understanding:

• * * * * * /path/to/script.sh
  Runs every minute.
• 0 3 * * * /usr/bin/backup.sh
  Runs daily at 3:00 AM.
• 0 9-17 * * 1-5 /usr/local/bin/check_service.py
  Runs every hour from 9 AM to 5 PM, Monday to Friday.
• */15 * * * * echo "Hello, CoddyKit!"
  Runs every 15 minutes.

Remember to replace /path/to/script.sh with your actual command or script path.

For very common scheduling needs, Cron provides special strings that are easier to read than the five-field syntax:

• @reboot: Run once at startup.
• @hourly: Run once an hour, at the beginning of the hour.
• @daily: Run once a day, at midnight.
• @weekly: Run once a week, at midnight on Sunday.
• @monthly: Run once a month, at midnight on the first day of the month.
• @yearly (or @annually): Run once a year, at midnight on January 1st.

These are great for simple, recurring tasks.

When cron runs a job, it uses a very minimal set of environment variables. This often means commands that work in your terminal might fail in cron.

To avoid issues:

• Always use absolute paths for commands and scripts (e.g., /usr/bin/php instead of php).
• You can define a PATH variable right inside your crontab file, e.g., PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
• Alternatively, set environment variables directly within your script.

By default, cron attempts to email any output (stdout and stderr) from a cron job to the user who owns the crontab. If you don't have an email system configured, this output might be lost or fill up log files.

It's best practice to explicitly redirect output:

• To discard all output: command > /dev/null 2>&1
• To append output to a log file: command >> /var/log/myjob.log 2>&1

The 2>&1 part redirects standard error (2) to the same location as standard output (1).

We've focused on personal user crontabs, managed with crontab -e. These are great for individual user tasks.

For system-wide tasks, administrators often use:

• /etc/crontab: The main system crontab, allowing tasks to run as specific users.
• /etc/cron.d/: Directory for separate cron files, often installed by applications.
• /etc/cron.hourly/, /etc/cron.daily/, etc.: Directories where scripts are placed to be run at those specific intervals by system cron.

These system-level options offer more control for server-wide automation.

You've learned the basics of crontab syntax. Let's see if you can decipher this cron job.

You've now mastered the essentials of scheduling tasks with Cron!

Here's what we covered:

• What is Cron: A time-based job scheduler.
• Crontab: Your personal file for defining cron jobs.
• Syntax: Understanding the 5 time fields and special characters (*, -, ,, /).
• Special Strings: Shortcuts like @hourly and @reboot.
• Best Practices: Using absolute paths and handling output.

With Cron, you can automate mundane tasks, ensuring your server runs smoothly and efficiently!