Re: [OMPI users] clarity on Comm_connect

Designation: Non-Export Controlled Content Another follow up. If I run all proxies on the same node as the dispatcher then it works. Even with all sensors spread to different nodes. If I force the proxies to another node, they all fail. Here is some more error output.

Re: [OMPI users] clarity on Comm_connect

Designation: Non-Export Controlled Content ...forgot to mention... I have a group of processes called sensors and a group of processes called proxies. A central dispatch process launches all of the sensors followed by all of the proxies. The sensors publish named ports and wait on

[OMPI users] clarity on Comm_connect

Designation: Non-Export Controlled Content Folks; Trying to do an MPI_Lookup_name. The call is surrounded by a try catch block. Even with the try catch block the calling process will still abort if the publishing process has not published the name. Is there a way to

Re: [OMPI users] Openmpi 2.0.1 build --with-psm2 failed on CentOS 7.2

Wonderful, thank you so much MAC! Limin On Wed, Oct 12, 2016 at 12:50 PM, Cabral, Matias A < matias.a.cab...@intel.com> wrote: > Hi Limin, > > > > One more detail. I advise to use a stable release: > > > > https://github.com/01org/opa-psm2/releases > > > > Regards, > > > > _MAC > > > > *From:*

Re: [OMPI users] Openmpi 2.0.1 build --with-psm2 failed on CentOS 7.2

Hi Limin, One more detail. I advise to use a stable release: https://github.com/01org/opa-psm2/releases Regards, _MAC From: users [mailto:users-boun...@lists.open-mpi.org] On Behalf Of Limin Gu Sent: Tuesday, October 11, 2016 7:33 PM To: Open MPI Users Subject: Re:

Re: [OMPI users] MPI Behaviour Question

After the responses I did more testing. Even $(hostname) and `hostname` get expanded on the first node. A script using echo (then any of them from the environment variable to the backticks works. I'm guessing all shell expansion on the CLI happens on the first node, from my limited testing. That