Re: test of install on mars

My reply is inline below...

On Jan 7, 2008 3:15 PM, Michael S. Vogeley <msv23@drexel.edu> wrote:

> This dies with error messages
> == Basin Client Paths ==
> Scripts Path: /home/vogeley/bin/basin/scripts
> which: no visit in
> (/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/4.1.1:/usr/i686-pc-linux-gnu/gcc-bin/4.1.1:/opt/blackdown-
> jdk-1.4.2.03/bin:/opt/blackdown-jdk-1.4.2.03
> /jre/bin:/home/vogeley/bin:/home/vogeley/xgobi/src)
> VisIt Path:
> ========================
> which: no visit in
> (/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/4.1.1:/usr/i686-pc-linux-gnu/gcc-bin/4.1.1:/opt/blackdown-
> jdk-1.4.2.03/bin:/opt/blackdown-jdk-1.4.2.03
> /jre/bin:/home/vogeley/bin:/home/vogeley/xgobi/src)
> scripts/basin_start.sh: line 121: ipcontroller: command not found
> Error launching the controller, exiting.
>
> OK, so visit is needed for basin remote? That's not what
>
> http://www.physics.drexel.edu/basin_trac/remote_trac/wiki/RemoteInstallationBin
> says.

Can you ensure that ipcontroller (as well as the other ip* programs) are on
your path?

I think, despite the other messages about visit stuff, that if the script is
able to find ipcontroller it will work or at least be closer to working :)

>
>
> BASIN CLIENT
> ------------
>
> Next, the client from binary.
> Start at page
>
> http://www.physics.drexel.edu/basin_trac/client_trac/wiki/ClientInstallationBin
> From
> http://www.physics.drexel.edu/basin_trac/client_trac/wiki/Releases
> download
> basin_client_i686_python2.5_1.2.1-beta_12_19_07.tar
> into my Download directory.
> Again, unpack into the /home/vogeley/bin/basin directory
> tar -xzf basin_client_i686_python2.5_1.2.1-beta_12_19_07.tar -C
> /home/vogeley/bin
>
> Will have to wait to get remote installed before testing this.
>
>
Received on Thu Jan 10 11:42:33 2008