Hi,
Am 08.12.2010 um 21:20 schrieb Ralph Castain:
> Afraid I'm not an x-forwarding expert... :-(
>
> Hopefully someone more knowledgeable can chime in.
>
>
> On Dec 8, 2010, at 12:54 PM, brad baker wrote:
>
>> Ya, I just tested -x as well, and it does indeed set the value of DISPLAY
>>
Ya, I just tested -x as well, and it does indeed set the value of DISPLAY
correctly for every process, every time I run it. Unfortunately the display
is still not behaving as desired. Sometimes they open, and sometimes they
don't.
I'm currently using openmpi-1.4.1 over infiniband on a Rocks
FWIW: I just tested the -x option on a multi-node system and had no problem
getting the value of DISPLAY to propagate. I was able to define it on the cmd
line, saw it set correctly on every process, etc.
This was with our devel trunk - not sure what version you are using.
On Dec 7, 2010, at
Thanks for your responses! I'm at home today so I can't actually do any
tests to 'see' if anything works. But I logged in remotely and I did as
Ralph suggested and ran env as my app. No process returned a value for
DISPLAY. Then I made a small program that calls getenv("DISPLAY") to run
with
Are you using ssh to launch OMPI between your nodes? (i.e., is mpirun using
ssh under the covers to launch on remote nodes)
If so, you might want to just set OMPI to use "ssh -X", which sets up SSH
tunneled X forwarding, and therefore it sets DISPLAY for you properly on all
the remote nodes
Hmmm...yes, the code does seem to handle that '=' being in there. Forgot it was
there.
Depending on the version you are using, mpirun could just open the display for
you. There is an mpirun option that tells us to please start each app in its
own xterm.
You shouldn't need forwarding if you
Without including the -x DISPLAY, glut doesn't know what display to open.
For instance, without the -x DISPLAY parameter glut returns an error from
each process stating that it could not find display "" (empty string). This
strategy is briefly described in the openmpi
Guess I'm not entirely sure I understand how this is supposed to work. All the
-x does is tell us to pickup an envar of the given name and forward its value
to the remote apps. You can't set the envar's value on the cmd line. So you
told mpirun to pickup the value of an envar called
