Cron fails on single apostrophe

Question

The following does work as expected:

date +\'%d-%b-%Y-%H-%M\'

28-Sep-2009-14-28

But none of the following 4 entries from crontab are working.

* *         


        

Answer 1

As long as there are no spaces in the format string supplied as an argument to date, you should not need the ticks at all.

date +%d-%b-%Y-%H-%M

should work.

Answer 2

You're using a syntax not supported by /bin/sh. Try invoking your preferred shell and passing the command as an argument.

Answer 3

There are four common causes for cron job commands to behave differently compared to commands typed directly into an interactive shell:

• Cron provides a limited environment, e.g., a minimal $PATH, and other expected variables missing.
• Cron invokes /bin/sh by default, whereas you may be using some other shell interactively.
• Cron treats the % character specially (it is turned into a newline in the command).
• The command may behave differently because it doesn't have a terminal available.

You must precede all % characters with a \ in a crontab file, which tells cron to just put a % in the command, e.g.

16 * * * * mysqldump myDB myTB > "/backup/ABCbc$(date +'\%d-\%b-\%Y-\%H-\%M').sql" 2> "/backup/ABCbc_errORS$(date +'\%d-\%b-\%Y-\%H-\%M').txt"

(As a separate matter, always put double quotes around a "$variable_substitution" or a "$(command substitution)", unless you know why not do it in a particular case. Otherwise, if the variable contents or command output contains whitespace or ?*\[, they will be interpreted by the shell.)