What OMPI version are you talking about?
We already trap SIGPIPE, but ignore it at the request of others (not sure what
version that was started). I believe a flag may exist to alter that behavior -
could easily be added if not.
On Nov 24, 2010, at 5:08 PM, Jesse Ziser wrote:
> Hello,
>
> I'
Hello,
I've noticed that OpenMPI does not seem to detect when something
downstream of it fails. Specifically, I think it does not handle
SIGPIPE or pass it down to its young, but it still prints an error
message every time it occurs.
For example, running a command like this:
mpirun -np 1
> -Original Message-
> From: users-boun...@open-mpi.org [mailto:users-boun...@open-mpi.org] On
> Behalf Of Bill Rankin
> Sent: 24 November 2010 15:54
> To: Open MPI Users
> Subject: Re: [OMPI users] MPI_Comm_split
>
> In this case, creating all those communicators really doesn't buy you
>
Hello all,Any help would be appreciated on the problem below.Starting openmpi 1.4.2 run stalls before any output to console. It is not every time, and in this case was on the 15th run of IMB-MPI1 version 3.2. There is another test running on the eth0 interface at the same time as this test. It i
In this case, creating all those communicators really doesn't buy you anything
since you aren't using any collective operations across all the subgroups you
would be creating.
For this sort of course-grained parallelism, your best bet is probably a
master/slave (producer/consumer, worker-pool)
