Linux Execute Cron Job After System Reboot

Posted on in Categories , last updated May 19, 2015

I am on Red Hat Enterprise Linux server. Is there is an easy way to run script or command at boot time after fresh reboot command?

crontab is the program used to install, deinstall or list the tables used to drive the cron daemon in Vixie Cron. Each user can have their own crontab, and though these are files in /var/spool/cron/crontabs, they are not intended to be edited directly. You or user can use crontab program to edit cron jobs.

Running job at startup (boot time)

You need to use special string called @reboot. It will run once, at startup after reboot command.

@reboot  /path/to/job
@reboot  /path/to/shell.script
@reboot  /path/to/command

This is an easy way to give your users the ability to run a shell script or command at boot time without root access. First, run crontab command:
$ crontab -e
# crontab -e -u UserName
# crontab -e -u vivek

Run a script called /home/vivek/bin/
@reboot /home/vivek/bin/

Start crond automatically at boot time

You also need to enable crond service via sys v / BSD init style system. Under RHEL / CentOS / Fedora, you need to use chkconfig (ntsysv) command to enable crond on boot:
# chkconfig crond on
## Commands to start/stop/restart crond ###
# service crond restart
# service crond start
# service crond stop

Under Debian / Ubuntu Linux use update-rc.d as follows to turn on service on boot:
# update-rc.d cron defaults
If you are using modern distro with systemd, try
# systemctl enable crond.service
### this to start/stop/restart crond on systmd enabled distro such centos 7.x/debian/ubutnu/arch ###
# systemctl start crond.service
# systemctl stop crond.service
# systemctl restart crond.service
# systemctl status crond.service

Save and close the file. For further information read out tutorial on cron jobs.

14 comment

  1. OK, But some caveats here.

    1. Only works after a reboot. If you do a shutdown, or if the box crashes (as in plug vs vacuum) …. and then start, it doesn’t get run.

    2. The @reboot command is not universal, especially missing on systems running micro or embedded Linux.

    3. There is an alternate. the file /etc/rc.local is a place were you can place a command string to be run on boot, regardless of the means by which the system went down. Yes I know many Linux purists in favor of SysV style init scripts. However for a quick on liner it’s perfect. Here also gets run if you do a warm restart (as in go to init level 1 and then back to 3 or 5). Best this works across a very wide if not all spectrum of Linux systems. Anything in this file is always the last thing to run prior to login prompt appearing.

    4. Write an init script, and put it in /etc/init.d with the appropriate run levels and timing. Harder to do and get right, somewhat, but it is the correct way to create an init entry. It also would allow for you to fine tune the timing. (need to run this job before something else gets started? Use this method)

  2. Nice..
    linuxrebel is just looks ..right…but will an normal .sh script run on boot up if we put it in specified run level script like rc3.d ?…or what we need to do to follow what Linuxrebel said above??

    Thanks Vk & Lr

  3. The @reboot command not working. Finally got this and using for my WordPress Site,
    # touch /etc/init.d/memcached
    # echo ‘#!/bin/sh -e’ >> /etc/init.d/memcached
    # echo ‘/usr/local/bin/memcached -d -m 128 -p 11211 -u nobody -l localhost’ >> /etc/init.d/memcached
    # chmod u+x /etc/init.d/memcached
    # echo ‘/etc/init.d/memcached’ >> /etc/rc.local

  4. On CentOS 5.6, an /etc/cron.d/rebootlog crontab containing

    @reboot root date >> /var/tmp/reboot.log

    Is run when the system restarts after the commands “reboot”, “shutdown -r”, “shutdown -h”, “halt” and after a power failure. I did not find a shutdown method where the job was not run when the system restarted.

    1. If Cron is running a custom script then in your script you can write to a log file. Something like echo “Starting cronjob + timestamp” and echo “Successfully finished cron job + timestamp”

  5. With grep, it’s a little bit different. For example, to move every files including a given type of datas:
    grep ‘<div id=' ./* | cut -f 1 -d":"|xargs -I {} mv {} ../YOUREP/{}

  6. great tip, tnx! Made my day & solved a problem I had.. :)
    Btw, I’ve just noticed a typo: command on redhat is “chkconfig” instead of “chekconfg”.

  7. Just an FYI…there’s a typo in the header of the word “startup”: “Running job at statup (sp.) (boot)”.

Leave a Comment