Any ideas on how to make the /etc/profile variables availabe to ksh scripts exectued from the cron.
they are availabel when I reference them from the ksh command prompt for the same user that owns the cron.
Cron runs is a very minimal environment that has little or nothing to do with the user's own environment. The best strategy I find is to place all important PATH variables etc explicitly in the job being called (or in a 'wrapper' script used by cron to call the job after execution of the environment-setting part). Also, it is best to use /full/path/to/program for things like cp and other commands to avoid any possibility that they will cause problems.
Hoep this helps.
The internet - allowing those who don't know what they're talking about to have their say.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.