{"id":63220,"date":"2022-03-28T09:01:17","date_gmt":"2022-03-28T09:01:17","guid":{"rendered":"https:\/\/www.cryptocabaret.com\/?p=63220"},"modified":"2022-03-28T09:01:17","modified_gmt":"2022-03-28T09:01:17","slug":"scheduling-tasks-with-the-linux-cron-command","status":"publish","type":"post","link":"https:\/\/www.cryptocabaret.com\/?p=63220","title":{"rendered":"Scheduling tasks with the Linux cron command"},"content":{"rendered":"

Scheduling tasks with the Linux cron command<\/span>
\nDon Watkins<\/a><\/span>
\nMon, 03\/28\/2022 – 03:00<\/span><\/p>\n

\n
Up<\/div>\n
Register<\/a> or Login<\/a> to like.<\/div>\n<\/div>\n
\n

Early in my Linux journey, I came to appreciate the numerous command-line utilities of the operating system and the way they streamlined regular tasks. For example, backing up applications on my Windows server frequently required expensive add-on software packages. By contrast, the tar<\/code> command makes backing up Linux relatively easy, and it’s powerful and reliable too.<\/p>\n

When backing up our school district email system, however, I faced a different challenge. Backups couldn’t occur during the workday or early evening because people were using the system. The backup had to occur after midnight, and it needed to be reliable. I was used to Windows Task Manager, but what was I going to use on Linux? That’s when I learned about cron.<\/p>\n<\/p>\n

\n
More Linux resources<\/div>\n
\n
Linux commands cheat sheet<\/a><\/div>\n
Advanced Linux commands cheat sheet<\/a><\/div>\n
Free online course: RHEL technical overview<\/a><\/div>\n
Linux networking cheat sheet<\/a><\/div>\n
SELinux cheat sheet<\/a><\/div>\n
Linux common commands cheat sheet<\/a><\/div>\n
What are Linux containers?<\/a><\/div>\n
Our latest Linux articles<\/a><\/div>\n<\/p><\/div>\n<\/p><\/div>\n

Scheduling tasks on Linux with cron<\/h2>\n

Cron is a daemon used to execute scheduled commands automatically. Learning how to use cron required some reading and experimenting, but soon I was using cron to shut down our email server, back up the data in a compressed tar file, then restart the email service at 3AM.<\/p>\n

The commands for a cron job are stored in the crontab file on a Linux system, which is usually found in \/etc\/crontab. Display the contents of your crontab file with $ crontab -l<\/code>.<\/p>\n

Edit the crontab file with $ crontab -e<\/code>.<\/p>\n

Some systems default to the Vi editor<\/a> for cron editing. You can override this setting using environment variables<\/a>:<\/p>\n

\n$ <\/span>EDITOR<\/span>=nano<\/span> crontab -e<\/span><\/code><\/span><\/pre>\n
All crontab commands have parameters denoted by an asterisk until you insert an integer value. The first represents minutes, then hours, day of the month, month of the year, and finally, day of the week.<\/p>\n
Comments are preceded by a hash. Cron ignores comments, so they’re a great way to leave yourself notes about what a command does and why it’s important.<\/p>\n
A sample cron job<\/h2>\n
Suppose you want to scan your home directory for viruses and malware with clamscan<\/a> every week on Monday at 10AM. You also want to back up your home directory every week on Tuesday at 9AM. Using cron and crontab files ensures that your system maintenance occurs every week whether you remember to run those utilities or not.<\/p>\n
Edit your crontab file to include the following, using your own username instead of “don” (my user name):<\/p>\n
\n
# Scan my home directory for viruses<\/span>
0<\/span> 10<\/span> *<\/span> *<\/span> 1<\/span> clamscan -ir<\/span> \/<\/span>home\/<\/span>don
# Backup my home directory<\/span>
0<\/span> 9<\/span> *<\/span> *<\/span> 2<\/span> tar<\/span> -zcf<\/span> \/<\/span>var\/<\/span>backups\/<\/span>home.tgz \/<\/span>home\/<\/span>don<\/div><\/div><\/pre>\n
If you’re using the nano editor, save your work with Ctrl+O<\/b> to write the file out and Ctrl+X<\/b> to exit the editor. After editing the file, use crontab -l<\/code> to list the contents of your cron file to ensure that it has been properly saved.<\/p>\n
You can create crontab jobs for any job required on your system. This takes full advantage of the cron daemon.<\/p>\n
Scheduling from the Linux command line<\/h2>\n
It’s no secret that the hardest part of cron is coming up with the right values for those leading asterisks. There are websites, like crontab.guru<\/a>, that dynamically translate cron time into human-readable translations, and Opensource.com has a cron cheat sheet<\/a> you can download to help you keep it straight.<\/p>\n
Additionally, most modern cron systems feature shortcuts to common values, including:<\/p>\n
This allows you to use the nano editor<\/a> to edit your personal crontab (if you don’t have one yet, one is created automatically for you).<\/p>\n