Thanks!
> On Jan 7, 2015, at 6:56 PM, Gilles Gouaillardet
> <gilles.gouaillar...@iferc.org> wrote:
>
> Ralph,
>
> honestly, i do not know if the standard says anything
> (all i can do for now is blame the coin ;-) )
>
> from now, i ll make a PR to update the man page (only master refers
> ompi_unique)
>
> Cheers,
>
> Gilles
>
> commit 7d2e3028d608163247975397a09f30dbe7bd192a
> Author: Ralph Castain <r...@open-mpi.org>
> Date: Wed Aug 14 04:24:17 2013 +0000
>
> Add unique info_key to documentation
>
> On 2015/01/08 11:51, Ralph Castain wrote:
>> Does the standard say anything about the default behavior? IIRC, we set it
>> this way because (a) we had no direction, and (b) it seemed just as
>> reasonable as the alternative (I believe we flipped a coin)
>>
>>
>>> On Jan 7, 2015, at 6:47 PM, Gilles Gouaillardet
>>> <gilles.gouaillar...@iferc.org> wrote:
>>>
>>> Well, per the source code, this is not a bug but a feature :
>>>
>>>
>>> from publish function from ompi/mca/pubsub/orte/pubsub_orte.c
>>>
>>> ompi_info_get_bool(info, "ompi_unique", &unique, &flag);
>>> if (0 == flag) {
>>> /* uniqueness not specified - overwrite by default */
>>> unique = false;
>>> }
>>>
>>> fwiw, and at first glance, i would have expected the default behaviour
>>> is to *not* overwrite (e.g. unique = true;).
>>>
>>> anyway, in order to get the expected result, the user program can be
>>> modified like this :
>>>
>>> MPI_Info info;
>>> MPI_Info_create(&info);
>>> MPI_Info_set(info, "ompi_unique", "true");
>>>
>>> and then invoke MPI_Publish_name() with info instead of MPI_INFO_NULL
>>>
>>> an updated version of the program
>>>
>>> Cheers,
>>>
>>> Gilles
>>>
>>> On 2015/01/08 10:12, Ralph Castain wrote:
>>>> Hmmm…I confess this API gets little, if any, testing as it is so seldom
>>>> used, so it is quite possible that a buglet has crept into it. I’ll take a
>>>> look and try to have something in 1.8.5.
>>>>
>>>> Thanks!
>>>> Ralph
>>>>
>>>>> On Jan 7, 2015, at 3:14 AM, Bernard Secher <bernard.sec...@cea.fr> wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> With the version openmpi-1.4.5 I got an error when I tried to publish
>>>>> the same name twice with the MPI_Publish_name routine
>>>>> With the version openmpi-1.8.4 I got no error when I published the same
>>>>> name twice with the MPI_Publish_name routine
>>>>>
>>>>> I used the attached script and source code to perform the test.
>>>>>
>>>>> With this test, it works well with openmpi-1.4.5, but I get a deadlock
>>>>> with openmpi-1.8.4. I can suppress the deadlock with openmpi-1.8.4 if I
>>>>> modify the shell script and add a "sleep 1" command between the 2 mpirun
>>>>> commands.
>>>>>
>>>>> Bernard
>>>>> <testMPI2.cxx><launch_testMPI2.csh>_______________________________________________
>>>>> users mailing list
>>>>> us...@open-mpi.org
>>>>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
>>>>> Link to this post:
>>>>> http://www.open-mpi.org/community/lists/users/2015/01/26114.php
>>>> _______________________________________________
>>>> users mailing list
>>>> us...@open-mpi.org
>>>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
>>>> Link to this post:
>>>> http://www.open-mpi.org/community/lists/users/2015/01/26117.php
>>> <testMPI2.cxx>_______________________________________________
>>> users mailing list
>>> us...@open-mpi.org
>>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
>>> Link to this post:
>>> http://www.open-mpi.org/community/lists/users/2015/01/26119.php
>> _______________________________________________
>> users mailing list
>> us...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
>> Link to this post:
>> http://www.open-mpi.org/community/lists/users/2015/01/26120.php
>
> _______________________________________________
> users mailing list
> us...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post:
> http://www.open-mpi.org/community/lists/users/2015/01/26121.php
