1) redirect stdout and stderr of the script some place
2) supply the full path of the script. ./scriptname is bad form. Makes the assumption that cron sets the working directory to the directory that the script resides in. May or may not be the case, but don't risk it.
3) Add a !# line to the script and remove sh from the command line in the crontab.
Dude, I faced the same problem few days back while executing a script..It ran perfectly fine from the command line but crontab wasn't able to execute it..
However when I inserted my environment variables into the script it ran from crontab..This may work out for you as well..Try it out..Just specify your environment into the script and it will work fine...
U can also try including ur ".profile" into the script with the addition of command inside ur script so that it can take all the environment variables defined for ur profile...
However if this doesn't work out you will have to set your environment manually inside the script to make it executable from cron...
"/tmp/crontabiGaaqa" 16 lines, 561 characters
3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57,60 * * * * /sicaklik.sh
crontab: error on previous line; number out of bounds.
crontab: errors detected in input, no crontab file generated.
How can I run every 3 minutes this script. Why do I give above error messages.