Gah. I didn't realize that my 1.4.x build was a *developer* build.
*Developer* builds give a *lot* more detail with plm_base_verbose=100
(including the specific rsh command being used). You obviously didn't get that
output because you don't have a developer build. :-\
Just for reference, he
Hi Jeff,
Thanks.
I tried as what you suggested. Here are the output:
>>>
yiguang@gulftown testdmp]$ ./test.bash
[gulftown:25052] mca: base: components_open: Looking for plm
components
[gulftown:25052] mca: base: components_open: opening plm
components
[gulftown:25052] mca: base: components_ope
The intent of the --prefix option (or using the full path name to mpirun) was
exactly for the purpose of not requiring changes to the .bashrc.
Can you run with "--mca plm_base_verbose 100" on your command line? This will
show us the exact rsh/ssh command line that is being executed -- it might
Greetings!
I have tried to run ring_c example test from a bash script. In this
bash script, I setup PATH and LD_LIBRARY_PATH(I donot want to
disturb ~/.bashrc, etc), then use a full path of mpirun to invoke mpi
processes, the mpirun and orted are both on the PATH. However,
from the Open MPI me
