>_ IzzyLab

Topic breakdown

For the kernel to exec() a file, the file must have the execute bit (x) set — without it cron will honestly try to run the script and get Permission denied, even if the crontab line itself is perfect. Diagnosing "cron is silent" goes by facts: is the job there (crontab -l), did cron try to run it (logs), and what state is the file in (ls -l). It's fixed by changing the file's mode with the appropriate tool; a missing shebang and a poor PATH inside cron are other common causes, but here it's the permissions.

What's checked

  1. Script is executable
  2. Cron job is in place
  3. cron ran the backup

What it looks like