LAM/MPI logo

LAM/MPI General User's Mailing List Archives

  |   Home   |   Download   |   Documentation   |   FAQ   |   all just in this list

From: Karl Hahn (hahnk_at_[hidden])
Date: 2003-08-05 02:37:18


Hi Jeff,

first of all: the problem is solved, thank you for your help!

> It's probably a little of both (ssh and LAM issues).
>
> You should probably check out the LAM FAQ in the section "Running LAM/MPI
> applications"; in particular, the following questions:
>
> - What directory does my LAM/MPI program run in on the remote nodes?
> - How does LAM find binaries that are invoked from mpirun?
> - Why doesn't "mpirun -np 4 test" work?
>
> Also, see the mpirun(1) man page which addresses these kinds of issues in
> detail (locating files, process environment, current working directory,
> etc.).

Ooops, I am sorry! To be honest I didn't use the FAQ and the man pages :-)
But thank you for the hint!

> You may also wish to run the following to ensure that your $PATH is really
> what you think it is:
>
> ssh s21 'echo $PATH'
>
> (note the quotes -- they're critical here) This will show you the $PATH
> that the remote LAM daemon (and therefore all programs that it starts) is
> getting.

Hhmmm, I think I should also have a (closer) look at the ssh man page.
I thought ssh s21 "echo $PATH" would do the job ...

> Finally, remember that your .tcshrc is only executed when you lamboot.
> So if you change the PATH in your .tcshrc after you lamboot, you'll need
> to lamboot again to see that change.

Okay - this really solved all my problems. I had to set other environment
as well, e.g., $LD_LIBRARY_PATH. I have restarted LAM and now my program
works.

Thanks a lot!

Charlie