Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

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.

Subject: Re: [OMPI users] Query regarding OMPI_MCA_ns_nds_vpid env variable
From: Ralph H Castain (rhc_at_[hidden])
Date: 2008-07-11 09:42:05

On 7/11/08 7:32 AM, "Ashley Pittman" <apittman_at_[hidden]>

> On Fri, 2008-07-11 at 07:20 -0600, Ralph H Castain wrote:
>> This variable is only for internal use and has no applicability to a user.
>> Basically, it is used by the local daemon to tell an application process its
>> rank when launched.
>> Note that it disappears in I wouldn't recommend looking for it. Is
>> there something you are trying to do with it?
> Recently on this list I recommended somebody use it for their needs.

Ah - yeah, that one slid by me. I'll address it directly.

>> Reason I ask: some folks wanted to know things like the MPI rank prior to
>> calling MPI_Init, so we added a few MPI envar's that are available from
>> beginning of process execution, if that is what you are looking for.
> It's also essential for Valgrind support which can use it to name
> logfiles according to rank using the --log-file=valgrind.out.%
> q{OMPI_MCA_ns_nds_vpid} option.

Well, it won't hurt for now - but it won't work with 1.3 or beyond. It's
always risky to depend upon a code's internal variables as developers feel
free to change those as circumstances dictate since users aren't supposed to
be affected.

I believe this is partly what motivated the creation of the MPI envars - to
create a vehicle that -would- be guaranteed stable for just these purposes.
The concern was that users were doing things that accessed internal envars
which we changed from version to version. The new envars will remain fixed.

Of course, that only applies to 1.3 and beyond... ;-)

> Ashley,
> _______________________________________________
> users mailing list
> users_at_[hidden]