Hence playing it save and including a blank [email protected] Suh, according to man page "cron requires that each entry in a crontab end in a newline character.If the last entry in a crontab is missing the newline, cron will consider the crontab (at least partially) broken and refuse to install it." This behavior will be invoked when editing then saving the crontab using the If neither the --lsbsysinit option nor the --regex option is given then the names must consist entirely of upper and lower case letters, dig‐ its, underscores, and hyphens.
If the last entry in a crontab is missing the newline, cron will consider the crontab (at least partially) broken and refuse to install it." (And the date at the end is 19 April 2010.)@barraponto This is actually a bug in new text editors.
The "newline" character is supposed to be a line termination character, so the final line in a text file is supposed to end in a newline character that doesn't get shown in the editor.
Vi and vim use the character correctly, and cron was built before the new editors started their odd behavior...
Some prefer to just use absolute paths to all the commands instead. Consider what happens if you want to run your script on a different system, and on that system, the command is in @pbr A sysadmin could unwittingly delete the root filesystem.
Please include one reason per answer - details about why it's not executed - and fix(es) for that one reason. commands that execute as expected from the shell but execute erroneously by cron.
You can't guard against sysadmins making silly mistakes.
If you install a newer version of an interpreter that is not backwards compatible, I'd expect breakage regardless.
The sane way to handle that is to install it as a different command. you have python version 2.x and install python 3, you install it as python3, not python.
And as for /opt/some App/bin, why on earth wouldn't it have sane permissions/ownership?