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.
> -----Original Message-----
> From: users-bounces_at_[hidden]
> [mailto:users-bounces_at_[hidden]] On Behalf Of Ralph Castain
> Sent: Wednesday, October 22, 2008 8:02 AM
> To: Open MPI Users
> Subject: Re: [OMPI users] OpenMPI runtime-specific
> environment variable?
> What I think Brian is trying to do is detect that his code
> was not launched by mpirun -prior- to calling MPI_Init so he
> can decide if he wants to do that at all. Checking for the
> enviro params I suggested is a good way to do it - I'm not
> sure that adding another one really helps. The key issue is
> having something he can rely on, and I think the ones I
> suggested are probably his best bet for OMPI.
Just closing the loop on this thread -- again thanks for all the good discussion. Ralph's comment here is exactly right. On some platforms, e.g., AIX/Poe/IBM MPI, we've historically been bitten as it's not safe to call MPI_Init when not running inside a job submitted to the queue and running in an MPI environment. I realize it's our (perhaps stubborn) choice to distribute MPI-linked binaries that have to work correctly in both serial (not just mpirun -np 1) and MPI-parallel mdoes, and that complicates things.