Silly Cron/Script Questions

From: Skulley, William (William.Skulley@rfets.gov)
Date: Tue Jun 04 2002 - 15:29:38 EDT


I have a cronjob:

0 0 * * * script.ksh arg1 arg2.`date +%y%m%d`

arg2 is an output filename. When run from cron, the file comes out "arg2."
with no date information tacked on. Running the exact same command line
from a shell (sh) prompt gets the date information properly (filename
arg2.020604). I get the following mail from cron:

*************************************************
Cron: The previous message is the standard output
      and standard error of the following crontab command:

script.ksh arg1 arg2.`date +

If I add double quotes and change the cron entry to:

0 0 * * * "script.ksh arg1 arg2.`date +%y%m%d`"

the job does not run and I get the following mail from cron:

sh: script.ksh arg1 arg2.: not found

*************************************************
Cron: The previous message is the standard output
      and standard error of the following crontab command:

"script.ksh arg1 arg2.`date +

What am I missing? I'm sure its something really obvious and silly but I
can't for the life of me see it.

Thanks
Bill Skulley



This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:43 EDT