On Wed, Jul 17, 2002 at 12:44:39PM -0600, Keary Suska wrote: > on 7/17/02 12:13 PM, [EMAIL PROTECTED] purportedly said: > > > If you're having a problem with running your scripts from cron, the answer > > is usually in your PATH environment variable or working directory - cron > > tends to run with different paths, and your script probably can't find > > libraries or other things it needs. > > Except that Perl does not rely on PATH and related variables to determine > module or loadable (.so) locations.
$PERLLIB > The cron problem could be permissions or > a CWD problem which would effect finding custom modules, if that is even an > issue, or several other reasons. If there was some information about what is > going wrong, perhaps a more sensible solution could be presented. Run a cron job with the command "env > /tmp/env" . Then set your environment to exactly that. (If you're using bash or some other sh-derivative, just ". /tmp/env" should do the trick.) Then debug the errors you get. -- Reinier
