Re: crond INC problem

This (/jobs/scripts/runscript) is a shell script, no? Try setting your path environment variable prior to calling the perl scripts. i.e.:

export PATH=/bin:/usr/bin:/usr/local/bin:/foo:/bar:/baz
perl /jobs/scripts/script.pl
perl /jobs/scripts/script.pl 3
[download]

Comment on Re: crond INC problem Download Code

Replies are listed 'Best First'.
Re^2: crond INC problem by Fletch (Bishop) on May 26, 2005 at 18:48 UTC
You might also consider sourcing your login environment rc file (presuming of course you use a shell that supports separate "environment rc" and "interactive rc" file). For example I use `zsh` and pure environment settings are in `~/.zshenv` while interactive aliases and prompts and what not are in `~/.zshrc`. If I need a cron job to have the same environment I'm used to at a prompt I just `source ~/.zshenv`. Even if your shell doesn't explicitly support this it might be worth breaking environment setup out into another file you can source from stuff run from `cron`. -- We're looking for people in ATL	[reply]

Replies are listed 'Best First'.

Re^2: crond INC problem
by Fletch (Bishop) on May 26, 2005 at 18:48 UTC

You might also consider sourcing your login environment rc file (presuming of course you use a shell that supports separate "environment rc" and "interactive rc" file). For example I use zsh and pure environment settings are in ~/.zshenv while interactive aliases and prompts and what not are in ~/.zshrc. If I need a cron job to have the same environment I'm used to at a prompt I just source ~/.zshenv. Even if your shell doesn't explicitly support this it might be worth breaking environment setup out into another file you can source from stuff run from cron.

--
We're looking for people in ATL

[reply]