I'd verify to see if you put the paths to these external programs into the PATH variable it would work. you can type
$export PATH = <path to progs1>:<path to progs2>:$PATH <path to progs> = the absolute path of the external programs you are calling. If there are more than one, like the above example, use colons to separate. If that works, then add these paths to your PATH variable at startup. If you are using the bash shell, I believe it's in .bashrc (could be .bash_profile, I'm not 100% sure and I'm at work). Whatever shell you are using, the startup files will be found in your Home directory. Anyway, look for the PATH definition and add to it. --- André Borman <[EMAIL PROTECTED]> wrote: > > > Hi there, > > I would like to know how I can get e.g. this crontab > entry > > * * * * * /usr/local/bin/foo -options arg1 arg2 > > to run right. > > Foo is a script that calls external programs itself > that need the mentioned > options and arguments. It seems that when foo is > executed, the external > programs are not executed because they're not in the > path. When I include > the absolute paths in the script everything works > fine, but that's not > really satisfying. __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/
