I’m not the OP, but I can explain how to use cron in like 4 sentences:
Edit cron with the command crontab -e, this opens your text editor. If you want your jobs to have environment variables, put those at the top. Put this header at the top: # m h dom mon dow command
It means minute, hour, day of month, month, day of week, command. Type in numbers for these values or a star which means all of them. Command is the command to be run.
And then with your explanation it goes: cron job doesn’t execute for reason, crontab -l lists not all jobs, someone else put cron job in whatever directory like cron.daily, you’ve added or removed empty line at the end and now nothing works, debian crond and redhat cronie ahave different quirks, etc., etc.
I’ve dealt with insane cron problems for so long that switching to timers was like *whoa i don’t need to suffer?*
I’m not the OP, but I can explain how to use cron in like 4 sentences: Edit cron with the command crontab -e, this opens your text editor. If you want your jobs to have environment variables, put those at the top. Put this header at the top: # m h dom mon dow command It means minute, hour, day of month, month, day of week, command. Type in numbers for these values or a star which means all of them. Command is the command to be run.
You can explain timers the same way.
And then with your explanation it goes: cron job doesn’t execute for reason,
crontab -llists not all jobs, someone else put cron job in whatever directory like cron.daily, you’ve added or removed empty line at the end and now nothing works, debian crond and redhat cronie ahave different quirks, etc., etc.I’ve dealt with insane cron problems for so long that switching to timers was like *whoa i don’t need to suffer?*