UNIX for Dummies Questions & Answers

append to your existing PATH ,the PATH of all commands those needed to run the script ;

export PATH=$PATHathto all commands


put this at the begining of script.sh

Sry for the smile symbol in the last post ....
For ex,

pathtoexp=/path/to/exp
export PATH=$PATH:$pathtoexp

If I didn't want to edit the script (vendors script) could I just source *.cshrc file or add this to the cron entry. Usually I log in as oracle(c shell), cd to directory and ./ the script.

I would prefer not to edit the script.

Could I make my own script and insert the source *.cshrc then list script or can I just and to crontab with a ;.

The .cshrc file I believe contains the correct PATH or it references another file which contains the PATHs for this and Oracle.

Yes, source your .cshrc, but don't source *.cshrc - specify what you are sourcing - if you put the wildcard in, you are asking for trouble.

Always specify exactly what you want -
source /export/home/oracle/.cshrc

#setup environment for cron usage
. /export/home/oracle/backup.ksh

got it to work when I found a file that set up oracle's enviroment.
Edited my original script and added a pointer to the env file(backup.ksh)

Can anyone tell me why you have to lead with a "." - I found it on the NET but don't know why it is used? To prevent forks??

What the fork is a fork?

If you run /export/home/oracle/backup.ksh like that, then it creates a child process that runs backup.ksh and then exits back to the parent process. You think, 'Well, I ran this, how come I don't see everything set up?!?!' It's because it ran as a child process - everything was set up there and then it exits.

Doing . /export/home/oracle/backup.ksh keeps it running as the parent process - and your environment gets set. It's the same as source /export/home/oracle/backup.ksh in csh. Read the man page on source.