Andrew,
the 2 seconds timeout is very likely a bug that was fixed, so i strongly
suggest you give a try to the latest 2.0.2 that was released earlier this
week.
Ralph is referring an other timeout which is hard coded (fwiw, the MPI
standard says nothing about timeout, so we hardcoded one to preve
We know v2.0.1 has problems with comm_spawn, and so you may be encountering one
of those. Regardless, there is indeed a timeout mechanism in there. It was
added because people would execute a comm_spawn, and then would hang and eat up
their entire allocation time for nothing.
In v2.0.2, I see i
I am using Open MPI version 2.0.1.
___
users mailing list
users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
What version of OMPI are you using?
> On Jan 31, 2017, at 7:33 AM, elistrato...@info.sgu.ru wrote:
>
> Hi,
>
> I am trying to write trivial master-slave program. Master simply creates
> slaves, sends them a string, they print it out and exit. Everything works
> just fine, however, when I add a d
> "George" == George Bosilca writes:
George> Why are you using system() the second time ? As you want
George> to spawn an MPI application calling MPI_Call_spawn would
George> make everything simpler.
Yes, this works! Very good trick... The system routine would be more
flexible, b
Why are you using system() the second time ? As you want to spawn an MPI
application calling MPI_Call_spawn would make everything simpler.
George
On Jul 3, 2014 4:34 PM, "Milan Hodoscek" wrote:
>
> Hi,
>
> I am trying to run the following setup in fortran without much
> success:
>
> I have an MP
Unfortunately, that has never been supported. The problem is that the embedded
mpirun picks up all those MCA params that were provided to the original
application process, and gets hopelessly confused. We have tried in the past to
figure out a solution, but it has proved difficult to separate th
