17 июн. 2015 г. · In my case, the jobs running as root weren't running because the root account password has changed. I changed the password and my cron jobs ran.

19 янв. 2016 г. · I do sudo crontab -e and see a bunch of cronjobs. If a cron exists in /etc/cron.d but not in sudo crontab -e does that mean it's not being ran?

23 окт. 2013 г. · When adding a cron configuration in /etc/cron.d/ or in /etc/crontab you have to add the username in which context the command should run, ...

28 янв. 2014 г. · @reboot : Run once after reboot. Thus your inference that the proper way to use @reboot is @reboot user_name command is correct.

6 июл. 2022 г. · General advice: remember that cron runs in a different environment that your command line. Try changing the commands to be more verbose and look at the cron ...

30 июл. 2015 г. · I discovered all /etc/cron.d files need to have permissions set to 600, otherwise cron reports an "INSECURE" MODE error.

11 июн. 2015 г. · Using Debian Jessie, I'm having trouble running a one line file I placed in /etc/cron.d. The file contains the following line: @reboot myuser ...

8 апр. 2018 г. · You will either need an init system ( runit , systemd , etc.) that can keep tabs on the process and (with appropriate configuration) restarts the daemon after ...

7 мая 2015 г. · It may be that there is an error somewhere in your /etc/crontab file (or another crontab file, if you use others) which is preventing it ...

22 нояб. 2017 г. · I have a set of scripts in /etc/cron.daily which anacron handled. They used to run fine every day but I noticed that they were not running recently.