Not that I know of...I would expect it to work.
On Jan 20, 2009, at 8:47 AM, jody wrote:
Thanks for the clarification.
Speaking of 'printenv' - i noticed that
even though $HOSTNAME is set on all of my machines:
aim-nano_03 ~ # echo $HOSTNAME
aim-nano_03
it does not appear in printenv's output:
aim-nano_03 opt # printenv | grep HOST
aim-nano_03 opt #
Is there something special about $HOSTNAME and how or when it is set?
Jody
On Tue, Jan 20, 2009 at 3:26 PM, Ralph Castain <r...@lanl.gov> wrote:
That was never an envar for public use, but rather one that was used
internal to OMPI and therefore subject to change (which it did).
There are a
number of such variables in the system - we try to indicate this by
not
exposing them via ompi_info. Of course, you can independently
discover them
with a printenv, but we would not recommend relying on them.
The list of reliable envars is provided here:
http://www.open-mpi.org/faq/?category=running#mpi-environmental-variables
Note that this begins with 1.3 and does not apply to any prior
releases.
Ralph
On Jan 20, 2009, at 4:43 AM, jody wrote:
Under 1.2.8 i could check
OMPI_MCA_ns_nds_vpid
to find out the process rank.
Under 1.3 that variable does not seem to exist anymore.
Is there an equivalent to hat variable in 1.3?
Have any other environment variables changed?
Thank You
Jody
_______________________________________________
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
_______________________________________________
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
_______________________________________________
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
