D
D
dvachek2014-12-12 01:10:48
Task Schedulers
dvachek, 2014-12-12 01:10:48

Cron doesn't run a job at 0 0 * * * but does everything else, what a miracle?

There are multiple jobs:
If the job has a time such as every 5 minutes, every minute, every hour, etc. then it runs successfully.
And if the task contains a specific hour or minute, it is not executed!
What is this nonsense?
*/5 * * * * - running (available in /var/log/syslog)
30 0 * * * - not running (missing in /var/log/syslog)
all rules are viewed in crontab -l
what should I do?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
I
Ivan Starkov, 2014-12-12
@icelaba

the cron file must end with a blank line,
unless otherwise specifically messed up,
see the cron doc
Although cron requires that each entry in a crontab end in a newline
character, neither the crontab command nor the cron daemon will detect
this error. Instead, the crontab will appear to load normally. However,
the command will never run.
So put enter at the end of the line

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question