environment variables version 3.2
 

Hi all,

I've installed the linux 3.2 version and I wonder how the environmental variables must be defined. Of course I can execute each time after a logout the setstar script but it should also work with defined variables in the login shell (.bashrc) Does someone know which variables must be defined in it??

thx

Re: environment variables version 3.2
 

Hi F.K.

not quite sure if I am answering what you are asking, but the star variables I have defined in my .bashrc files are as follows,

export STARVER=v3150

export STARDIR=/path to you star directory/$STARVER

export PATH=$PATH:$STARDIR/bin

export LM_LICENSE_FILE=$STARDIR/license/license.dat

If you are using ABSOFT fortran compiler you alos need to set the following variables,

export ABSOFT=/path to your ABSOFT directory

export PATH = $PATH:$ABSOFT/bin

If you need more help on how to write the .bashrc file checkout the net for examples.

Hope this helps :)

Re: environment variables version 3.2
 

... not at all, since it is very different for Version32 :(

Re: environment variables version 3.2
 

Your safest bet is to execute the setstar script directly out of your .cshrc or .bashrc. If it works that way, why is it necessary to redefine everything yourself?

Re: environment variables version 3.2
 

Steve's right: setstar is effectively just a shell script which sets the environment variables, so it's exactly what is required. Why re-invent the wheel?

Re: environment variables version 3.2
 

It takes more than a minute to execute the script on my machine. Also other people have the same problem.

Re: environment variables version 3.2
 

Yes , 1 minute or more and this seams to be a long time for defining variables. From my point of view there is absolutely no advantage in starting scripts where nobody knows what actually happens.

Re: environment variables version 3.2
 

1 minute or so on my Linux box, much less on a Sun. The Sun CDE desktop also has a new button after installation where you can start starlaunch without prior opening a shell and executing setstar. Anybody been able to create this button on a Linux machine? Regards Alex

Re: environment variables version 3.2
 

starlaunch -icon will create a desktop icon for you.

Re: environment variables version 3.2
 

Thank you Brian, but my description wasn´t complete. Sorry. This command worked well on a Sun, but Suse 9 gives only error messages. No icon on my desktop :(. Does it create an icon at your Linux? Best regards Alex

Re: environment variables version 3.2
 

I work on a RH 3.0 linux box and the time to run the script is negligible. I can't even see the time. I bet there is some sort of network timeout involved on your machines. Is star located on a auto-mounted file system that has to mount first before it can execute? I would take the script, turn on verbose mode and see exactly what operation it sticks on.

Re: environment variables version 3.2
 

Hi Steve,

I think that it is the time which is needed to check the license server. I run all locally. When I first tried v32 I was sure that it does not work until someone from the support told me to wait for such a long time.

Re: environment variables version 3.2
 

Hi Jorn, Apparently setstar more or less just runs the starenv script. I looked in there and found no license server checks at all. Its sets a bunch of environmental variables, and changes your path. I'm not sure why any of that would take a long time. I add a line

set -x

near the top to see what gets executed. Steve

Re: environment variables version 3.2
 

Jorn, One of the steps in the starenv script is

rsh localhost

I found that causes problems on some machines here but not others. I think the script might be hanging at that point until the rsh times out.

Steve

Re: environment variables version 3.2
 

Thanks for that Steve,

I solved the problem by deleting the "rsh" command and linking ssh to rsh.

After that the "ssh localhost" has to be run one time manually and then it works (for me). Maybe there are some side-effects for parallel execution on a cluster.

What do you think about dropping all the rlogin stuff and using slogin instead?

Re: environment variables version 3.2
 

I think slogin probably has just as many problems as rlogin - just different ones. I've been trying ssh and slogin around here with also mixed success.