On Mar 2, 2012, at 3:23 PM, Yiguang Yan wrote:
> It turns out that the "-x" option should be put on each line of the app file
> if app file is used.
>
>
> So from tests (a),(b),(c), if I am using app file, the PATH and
> LD_LIBRARY_PATH are only passed to slave node
> when the "-x" is set
It turns out that the "-x" option should be put on each line of the app file if
app file is used.
OK, now test results on our cluster, in case this may be useful to some Open
MPI users(Open MPI 1.4.3 used on
my system):
(1) If I run mpirun command from command line as Jeff's foo test,
On Mar 2, 2012, at 2:50 PM, Ralph Castain wrote:
>> Ralph and I just had a phone conversation about this. We consider it a bug
>> -- you shouldn't need to put --prefix in the app file. Meaning: --prefix is
>> currently being ignored if you use an app file (and therefore you have to
>> put
On Mar 2, 2012, at 10:50 AM, Jeffrey Squyres wrote:
> On Mar 2, 2012, at 9:48 AM, Yiguang Yan wrote:
>
>> (All with the same test script test.bash I post in my previous emails, so
>> run with app file fed to mpirun command.)
>>
>> (1) If I put the --prefix in the app file, on each line of it,
On Mar 2, 2012, at 9:48 AM, Yiguang Yan wrote:
> (All with the same test script test.bash I post in my previous emails, so run
> with app file fed to mpirun command.)
>
> (1) If I put the --prefix in the app file, on each line of it, it works fine
> as Jeff said.
>
> (2) Since in the manual,
We'll take a look at the prefix behavior. As to the btl, you can always just
force it: for example, -mca btl sm,self,openib would restrict it to shared
memory and IB.
On Mar 2, 2012, at 7:48 AM, Yiguang Yan wrote:
> Hi Jeff, Ralph--
>
> Please let me follow the thread, here are what I
Hi Jeff, Ralph--
Please let me follow the thread, here are what I observed:
(All with the same test script test.bash I post in my previous emails, so run
with app file fed to mpirun command.)
(1) If I put the --prefix in the app file, on each line of it, it works fine as
Jeff said.
(2) Since
I don't know - I didn't write the app file code, and I've never seen anything
defining its behavior. So I guess you could say it is intended - or not! :-/
On Mar 1, 2012, at 2:53 PM, Jeffrey Squyres wrote:
> Actually, I should say that I discovered that if you put --prefix on each
> line of
> Actually, I should say that I discovered that if you put --prefix on each
> line of the app context file, then the first
> case (running the app context file) works fine; it adheres to the --prefix
> behavior.
Yes, I confirmed this on our cluster. It works with --prefix on each line of
the
Actually, I should say that I discovered that if you put --prefix on each line
of the app context file, then the first case (running the app context file)
works fine; it adheres to the --prefix behavior.
Ralph: is this intended behavior? (I don't know if I have an opinion either
way)
On Mar
Hi Ralph,
Thanks, here is what I did as suggested by Jeff:
> What did this command line look like? Can you provide the configure line as
> well?
As in my previous post, the script as following:
(1) debug messages:
>>>
yiguang@gulftown testdmp]$ ./test.bash
[gulftown:28340] mca: base:
What did this command line look like? Can you provide the configure line as
well?
On Mar 1, 2012, at 12:46 PM, Yiguang Yan wrote:
> Hi Jeff,
>
> Here I made a developer build, and then got the following message
> with plm_base_verbose:
>
> [gulftown:28340] mca: base: components_open:
Hi Jeff,
Here I made a developer build, and then got the following message
with plm_base_verbose:
>>>
[gulftown:28340] mca: base: components_open: Looking for plm
components
[gulftown:28340] mca: base: components_open: opening plm
components
[gulftown:28340] mca: base: components_open: found
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,
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:
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
17 matches
Mail list logo
