On Redhat and CentOS.


. OR RHEL/CentOS 5.


Therefore, rather than scheduling the reboot command, I recommend scheduling the shutdown command so it warns the user.

. Jul 15 20:07:45 RavenWing cron[1026]: (CRON) INFO (Running @reboot jobs) Jul 15 20:07:45. The following command helps: crontab -e.


As has been pointed out by sr_, though, perhaps you are tackling this in the wrong way, and a proper init. Share. .

daily , /etc/cron. After a while you should see a new cron.


editcrontabConfiguration: # /etc/crontab: system-wide crontab # Unlike any other crontab you don't have to run the `crontab' # command to install the new version when you edit this file # and files in /etc/cron.

,,, then try add some sleep for moment may can help. Share.

04. If it's root's crontab and not the user's: sudo crontab -e.

WHITE PAPER MANDIANT Linux Endpoint Hardening to Protect Against Malware and Destructive Attacks 3 The Linux operating system and supporting applications are becoming a prime target for adversaries.
daily , /etc/cron.

comment #1:.

sudo nano /etc/crontab.

. service manpage. I'm paraphrasing the cron manual here for the short version: As mentioned, crontab -e, the preferred method, will notify cron that something changed.

service. Restart. . It's free to sign up and bid on jobs. .

It's free to sign up and bid on jobs.

Nov 4, 2009 · In your cron job, check that the PID-file exists. While troubleshooting, you may try restarting the cron service as well.


1) at the command line type which reboot.

OR RHEL/Centos Linux 7.