yes and no,. So first, here is a quick fix for you: if you start the
server using
mpirun -np 2 -mca coll ^inter ./server
your test code finishes (with one minor modification to your code,
namely the process that is being excluded on the client side does need a
condition to leave the while loop as
On 3/25/12 5:22 PM, "Hameed Alzahrani" wrote:
> I installed open MPI on Linux cluster which consist of three machines. I want
> to ask how can I check that open MPI work correctly and is there a special
> configurations that I need to set to make the machines connect to each other
> because I jus
Arghh. You're right...
thx a lot!
Le 26 mars 2012 15:36, Ralph Castain a écrit :
> How did you configure OMPI? Did you inlaced --with-tm so that the native
> Torque support was built? If you do, then you shouldn't need to add a
> -machinefile to your cmd line as we'll automatically pickup t
Hi Edgar,
Did you take a look at my code? Any idea about what is happening? I did a
lot of tests and it does not work.
Thanks
On Tue, Mar 20, 2012 at 3:43 PM, Rodrigo Oliveira wrote:
> The command I use to compile and run is:
>
> mpic++ server.cc -o server && mpic++ client.cc -o client && mpir
How did you configure OMPI? Did you inlaced --with-tm so that the native Torque
support was built? If you do, then you shouldn't need to add a -machinefile to
your cmd line as we'll automatically pickup the allocation.
If you run your second way:
> /appl/mpi/openmpi/1.4.4/bin/mpirun -n $NUMPROC
Hi,
My problem:
On our cluster, openmpi 1.4.4 is installed. We are using the module
environment so I have created a module file to set up openmpi:
prepend-path PATH /appl/mpi/openmpi/1.4.4/bin
prepend-path LD_LIBRARY_PATH /appl/mpi/openmpi/1.4.4/lib
prepend-path MANPATH /appl/mpi/openmpi/1.4.4/sha
