[mvapich-discuss] Is there a way to have mpiexec (hydra) export '-env' by default?

[Jonathan Perkins]

On Mon, Sep 15, 2014 at 04:36:48PM -0400, Mehmet Belgin wrote:
> Hi Jonathan
> 
> > Actually, mpiexec (hydra) exports the the environment by default.  We
> > added the -export option to mpirun_rsh in order to give an operating
> > mode similar to mpiexec.
> 
> Oh, I wonder why it is not the case for us then. We have to explicitly
> use -env to make sure the the env is exported. Is there a compile or
> runtime parameter that influences this behavior that we might have
> toggled unintentionally?

Hmm, that seems strange.  Maybe you had a test case where a special
variable was involved?  Below is a link to some information on how
mpiexec (hydra) handles environment variables.

https://wiki.mpich.org/mpich/index.php/Using_the_Hydra_Process_Manager#Environment_Settings

> 
> 
> 
> On Sep 15, 2014, at 4:32 PM, Jonathan Perkins <perkinjo at cse.ohio-state.edu> wrote:
> 
> > On Mon, Sep 15, 2014 at 03:58:14PM -0400, Mehmet Belgin wrote:
> >> Hi everyone,
> >> 
> >> I was wondering if it is possible to make the "-env" default behavior for hydra (using a runtime or compile time config). Currently users need to remember providing this parameter to mpirun and sometimes things gets forgotten. I know that the same functionality ('-export') for mpirun_rsh was made default with 2.0 and I was wondering if there is a specific reason why hydra does not do the same?
> >> 
> >> Otherwise, I am considering a wrapper for mpirun, but I *really* don't like wrappers! :)
> > 
> > Actually, mpiexec (hydra) exports the the environment by default.  We
> > added the -export option to mpirun_rsh in order to give an operating
> > mode similar to mpiexec.
> > 
> > -- 
> > Jonathan Perkins
> 

-- 
Jonathan Perkins