Shell Programming and Scripting

Could you create a cronjob like this

Code:

X Y * * * /tmp/test.sh 1 2 3 2> /dev/null > /dev/null

Replace X and Y by the proper times to make the cron run as soon as possible

Code:

cat /tmp/test.sh
#!/usr/bin/ksh

echo $# > /tmp/log
echo $@ >> /tmp/log
echo $* >> /tmp/log

And post the output of /tmp/log

What is in .profile? My guess is that .profile is eating the argument somehow.

Please see my replies below:

Reply to [MA]Flying_Meat:

Your guess is my guess. Somehow the cron entry is taking the parmeter 2 as redirection (to /dev/null). Actually I tested with assigning $1 to a variable immediately also inside the script. That did not work either.

Reply to sb008:

Here is the ouput from test.sh script you provided.
3
1 2 3
1 2 3

Reply to Perderabo:

There is nothing special in .profile, except export statements for Oracle.

Still could not figure out what the problem was. Any help is appreciated.

Thanx..
-Bheem

Try to place the command within double quotes:

Code:

15 5 * * * "/appl/scripts/MyScript.sh 2" 2>/dev/null >/dev/null

Regards

Clearly the arguments are passed correctly to the script. Also the count for the number of arguments is correct.

As Perderabo stated the most likely candidate to cause your problem is the ".profile".

Could you change the "test.sh" script into:

Code:

cat /tmp/test.sh
#!/usr/bin/ksh

echo $# > /tmp/log
echo $@ >> /tmp/log
echo $* >> /tmp/log

. ~/.profile # for cron job environment visibility

echo $# >> /tmp/log
echo $@ >> /tmp/log
echo $* >> /tmp/log

Ofcourse the question is now whether the echo commands produce the same output prior and after executing the .profile

Thanks to sb008, Franklin52, Perderabo, roopla and Flying_Meat for responding to my post.

This problem is solved. I forgot to set $1 to a variable and that worked. Also, I forgot to mention that MyScript.sh was calling another script which could not find the input parameter. Now eveything runs fine.

Thanks once again to all.
-Bheem