{"id":60,"date":"2008-08-04T04:30:40","date_gmt":"2008-08-04T09:30:40","guid":{"rendered":"http:\/\/yourlinuxguy.com\/?p=60"},"modified":"2008-07-29T09:09:14","modified_gmt":"2008-07-29T14:09:14","slug":"how-can-i-set-up-a-cron-job-scheduled-task-quickly","status":"publish","type":"post","link":"https:\/\/yourLinuxGuy.com\/?p=60","title":{"rendered":"How can I set up a cron job (scheduled task) quickly?"},"content":{"rendered":"

So you have a task that you want to run regularly on Linux\/Unix. It could be a single commend, or a script that you prepared in advance that contains all the command you need run. What you need to do is to set up a “Cron job”. Cron is a system that, when the cron<\/code> program is running, reads a “tab” file for the instructions it needs, so that it can know *when* to execute *what*.<\/p>\n

How cron works – Old School<\/strong><\/p>\n

The standard “Old School” design has cron<\/code> reading a tab file that is named after any given valid user (we’ll just focus on root for now), in a directory like:<\/p>\n

\/var\/spool\/cron\/tabs<\/code> or \/var\/spool\/cron\/crontab<\/code><\/p>\n

…depending on your distro\/version. The tab file contains single-line instructions in the form of:<\/p>\n

minute hour day-of-month month day-of-week command<\/code><\/p>\n

…whereas the smallest increment of time cron<\/code> can utilize is one minute, and “command” is either your single command or a script, preferably with the full path. Asterisks can be used in place of any given date\/time stamp. For much more detail on the crontab<\/code> layout, see “man 5 crontab<\/code>“… and don’t forget the 5<\/code>!<\/p>\n

Here is an example. Say you had written a script that you wanted to run every morning at 6:10am. You would have the following in your crontab<\/code>:<\/p>\n

10 6 * * * \/home\/jpavlov\/bin\/myScript.bash<\/code><\/p>\n

How cron works – Modern<\/strong><\/p>\n

Most of this post will focus on the “Old School” cron<\/code> method, except for this section.<\/em> The modern method of cron<\/code> is very similar, and in fact on many distros, you have both methods available to you. In this version though, the cron<\/code> tab file is located at has a slightly place (\/etc\/crontab<\/code>) that does not directly matter to you, because you do not enter items in this tab to get them executed. Because this tab is nothing but a “caller” to other scripts that execute items in a series of other directories, all under \/etc\/<\/code>: cron.hourly<\/code>, cron.daily<\/code>, cron.weekly<\/code>, and cron.monthly<\/code>. Any executable files in these directories will be executed at the interval after which they are named.<\/p>\n

So, for instance, if you wanted a script to run daily, you can just copy the script into the \/etc\/cron.daily<\/code> directory (or create a link to it from there with ln -s<\/code>) and it will be run as root<\/code> at the next daily interval. If you only want a command executed, you can either add it to \/etc\/crontab<\/code> (not recommended, and it has a slightly different syntax, which I’m not going into), or just create a two-line script and do what I already described.<\/p>\n

Ah, but “what *time* to they start”, you ask? This is dictated (or not) by entries in the \/etc\/sysconfig\/cron<\/code> file, and I’ll allow you to read that and spare you more detail here. Just know that if you haven’t modified that file, the jobs run shortly after you boot, and the cron<\/code> clock is maintained off that time forward.<\/p>\n

How to view or edit the crontab<\/code><\/strong><\/p>\n

To view (list) the “Old School” crontab<\/code>, just do this:<\/p>\n

crontab -l -u user<\/code><\/p>\n

…and you can leave off the “-u user<\/code>” if you want to view your own crontab.<\/p>\n

DO NOT edit the crontab<\/code> files directly (unless you *really* know what you’re doing). To edit the crontab<\/code> file, do this:<\/p>\n

crontab -e -u user<\/code><\/p>\n

This will launch an editor for you to use to modify the crontab<\/code> file. By design, cronta<\/code>b on Linux\/Unix machines will use the editor specified by the system variable “EDITOR<\/code>” to open the file. You can find out which one you have set (likely vi<\/code>\/vim<\/code>) by typing echo $EDITOR<\/code>. If none is specified, it is vi<\/code>\/vim<\/code>.<\/p>\n

If you don’t like vi<\/code>, and prefer gedit<\/code> or something like it, you can modify that variable like this:<\/p>\n

EDITOR=gedit;export EDITOR<\/code><\/p>\n

…which can be made system-wide permanent by adding it to \/etc\/profile<\/code> or similar.<\/p>\n

Email behavior<\/strong><\/p>\n

I just want to mention how cron<\/code> integrates email notifications… When a job in the crontab<\/code> is executed, if there is any output, by default it is sent to root<\/code> (as dictated by your system, and any aliases, bla bla bla). A couple important points about that:<\/p>\n

    \n
  1. The email destination may be changed *per crontab<\/code>*, not per job. Just change (or add) a line like this to the top of the tab: MAILTO=jpavlov@yourLinuxGuy.com<\/code><\/li>\n
  2. Also, your command or script might dump a lot of output (like debugging) that you may not want sent in a result email. So, the output of a job can be suppressed by adding a redirector at the end of the job line. I’ll demonstrate by updating the crontab<\/code> line from above with the redirector (all on one line):<\/li>\n<\/ol>\n

    10 6 * * * \/home\/jpavlov\/bin\/myScript.bash > \/dev\/null 2>&1<\/code><\/p>\n

    And that’s our lesson for today folks. Phew, that was a lot, but it really isn’t that complicated once you’re used to it… like anything else, I suppose.<\/p>\n

    If I missed anything, make sure and let me know!<\/p>\n

    \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"

    So you have a task that you want to run regularly on Linux\/Unix. It could be a single commend, or a script that you prepared in advance that contains all the command you need run. What you need to do…
    Read more<\/a><\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[46,11,47],"tags":[],"class_list":["post-60","post","type-post","status-publish","format-standard","hentry","category-cron","category-intermediate","category-linuxgeneral"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pnjn1-Y","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=\/wp\/v2\/posts\/60","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=60"}],"version-history":[{"count":4,"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=\/wp\/v2\/posts\/60\/revisions"}],"predecessor-version":[{"id":64,"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=\/wp\/v2\/posts\/60\/revisions\/64"}],"wp:attachment":[{"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=60"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=60"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/yourLinuxGuy.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=60"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}