topic modifying calling environment from ksh script in Operating System - HP-UX

modifying calling environment from ksh script

Ben Spencer — Tue, 27 Mar 2001 18:36:19 GMT

at the end of a ksh script I went to set the directory that the user will be in after the script ends.

I can cd to the directory but when the script ends it reverts to the calling environment. I could source the script rather than execute but that is not acceptable. The user will never remember to source it.

Is there any way I can affect the calling environment from within a ksh script?

Thanks.
henry, hwollman@moody.edu

Re: modifying calling environment from ksh script

Jesper Sivertsen — Tue, 27 Mar 2001 18:50:04 GMT

You have to source the script to get it to work, but you could make an alias for the script like:
alias script='. script'

Good luck
Jesper

Re: modifying calling environment from ksh script

f. halili — Tue, 27 Mar 2001 18:59:32 GMT

Try to use a dot script.

Here's an example.
1) Create a script myfile ( in your home directory )
# vi myfile
root=/
cd $root
echo "hello"
2) Run the script
# . myscript
3) check your present dir
# pwd
/
4) You should be in the root directory now.

------ fnhalili

Re: modifying calling environment from ksh script

Ben Spencer — Tue, 27 Mar 2001 21:39:52 GMT

Not what I wanted to hear, but if the only way to do it is the dot command then I am stuck.

Thanks.

Re: modifying calling environment from ksh script

Bruce Regittko_1 — Wed, 28 Mar 2001 02:01:56 GMT

Hi,

Sorry, but Jesper is right. You will have to source the script. An alias is probably your best bet. Remember, if the user is running the C shell, the command is

source script

and not the "dot".

--Bruce

Re: modifying calling environment from ksh script

Rajeev Tyagi — Wed, 28 Mar 2001 14:12:44 GMT

When you execute a program from shell it forkes a new process and it can take the environment variables from parent but viceversa is not possible and that is why when you come out of the child shell you loose all setting for child shell. So the only way is to source it with a . command.

Eg. #. <Script-name>