In this article we describe How to Create and Manage Cron Jobs on Linux. Cron is one of Linux’s most useful tools and a developer favorite because it allows you to run automated commands at specific periods, dates, and intervals using both general-purpose and task-specific scripts. Given that description, you can imagine how system admins use it to automate backup tasks, directory cleaning, notifications, etc.
Cron jobs run in the background and constantly check the
/etc/crontab file, and the
/var/spool/cron/ directories. The cron files are not supposed to be edited directly and each user has a unique crontab.
How then are you supposed to create and edit cron jobs? With crontab commands. The crontab is the method you use to create, edit, install, uninstall, and list cron jobs.
The command for creating and editing cron jobs is the same and simple. And what’s even cooler is that you don’t need to restart cron after creating new files or editing existing ones.
$ crontab -e
Just as it is with any language, working with cron is a lot easier when you understand its syntax and there are 2 formats you should know:
A B C D E USERNAME /path/to/command arg1 arg2 OR A B C D E USERNAME /root/backup.sh
Explanation of above cron syntax:
- A: Minutes range: 0 – 59
- B: Hours range: 0 – 23
- C: Days range: 0 – 31
- D: Months range: 0 – 12
- E: Days of the week range: 0 – 7. Starting from Monday, 0 or 7 represents Sunday
- USERNAME: replace this with your username
- /path/to/command – The name of the script or command you want to schedule
That’s not all. Cron uses 3 operator symbols which allow you to specify multiple values in a field:
(*): specifies all possible values for a field
- The comma
(,): specifies a list of values
(-): specifies a range of values
(/): specifies a step value
Now that you know Cron’s syntax and operators, let’s see some cron examples.
Cron Job Examples
The first step to running cron commands is installing your crontab with the command:
# crontab -e
/root/backup.sh at 3 am every day:
0 3 * * * /root/backup.sh
script.sh Runing at 4:30 pm on the second of every month:
30 16 2 * * /path/to/script.sh
/scripts/phpscript.php at 10 pm during the week:
0 22 * * 1-5 /scripts/phpscript.php
perlscript.pl at 23 minutes after midnight, 2am and 4am, everyday:
23 0-23/2 * * * /path/to/perlscript.pl
Linux command Run at 04:05 every Sunday:
5 4 * * sun /path/to/linuxcommand
List cron jobs.
# crontab -l OR # crontab -u username -l
Delete all crontab jobs.
# crontab -r
Delete Cron job for a specific user.
# crontab -r -u username
Strings in Crontab
Strings are among the developer’s favorite things because they help to save time by eliminating repetitive writing. Cron has specific strings you can use to create commands quicker:
@hourly: Run once every hour i.e. “0 * * * *“
@midnight: Run once every day i.e. “0 0 * * *“
@daily: same as midnight
@weekly: Run once every week, i.e. “0 0 * * 0“
@monthly: Run once every month i.e. “0 0 1 * *“
@annually: Run once every year i.e. “0 0 1 1 *“
@yearly: same as @annually
@reboot: Run once at every startup
For example, this is how to backup your system every day:
At this point, you have all you need to create and manage system tasks using Cron. You can now begin to set up and maintain several environments using scheduled commands.
How much of a Cron user are you? And are there any details you can contribute to the article? The discussion box is below.
Also, you can read Ubuntu’s article on how to use Cron here. It has resources that you might find useful.