This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
But sorry why in the homepage is written:
"Features implemented or in
short-term development for Open MPI include:
Full MPI-2 standards
"short-term" not scheduled? the Client-Server is the
most innovative spawning method in MPI2, and this is not very good that
OpenMPI don't have it if it wants become the "BEST" MPI2 distribuition
today available, for this moment MPICH2 and LAM are the best for
stability and functionality!
>Data: 7-set-2006 11.25 PM
>A: "Open MPI Developers"
>Ogg: Re: [OMPI devel] MPI2 Client-Server routines
>On 9/7/06 3:12 PM, "Eng. A.A. Isola" <alfonso.isola_at_tin.
>>> Second, you can not use right now
>>> accross multiple jobs, this is
unfortunatly a known bug.
>> This is a
tremendous news1 for me!!
>> But when you will
>> resolve this
>We don't have a schedule yet for resolving this - we have
>fixes in place in a prototype system, but we aren't
certain when those will
>move to the public release.
>> Then the
unique way is to use the
>> accept/connect routines with orte
>At the moment, that *should* work - however, it has not
been fully tested as
>the system evolves. Hopefully, it will help for
>devel mailing list