I have akorn shell job that I can run manually but when I run via cron it starts and finishes, but does not do what it does when I run it manually.
Any ideals on why this is happening?
first guess would be an environment variable set in your shell but not set at the time of cron entry execution- you can put a 2>/tmp/myscript.err at the end of the script in the cron line to pipe the errors to a file you can look at
i.e.
1 * * * * /scripts/myscript.ksh 2>/tmp/myscript.err
Sure. It is the environment variables that get defined in .profile, and so on during login.
If you execute the set command from both "situations", live and cron, and redirect each output to separate files you will see differences.
Thanks everyone, I appreciate your help, this site is very helpful.
I had to include the execution of a particular profile that gets executed within my own profile.