Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

From: Brian W. Barrett (brbarret_at_[hidden])
Date: 2007-11-05 16:57:19

This is extremely tricky to do. How do you know which environment
variables to forward (foo in this case) and which not to (hostname).
SLURM has a better chance, since it's linux only and generally only run on
tightly controlled clusters. But there's a whole variety of things that
shouldn't be forwarded and that list differs from OS to OS.

I believe we toyed around with the "right thing" in LAM and early on with
OPen MPI and decided that it was too hard to meet expected behavior.


On Mon, 5 Nov 2007, Tim Prins wrote:

> Hi,
> After talking with Torsten today I found something weird. When using the SLURM
> pls we seem to forward a user's environment, but when using the rsh pls we do
> not.
> I.e.:
> [tprins_at_odin ~]$ mpirun -np 1 printenv |grep foo
> [tprins_at_odin ~]$ export foo=bar
> [tprins_at_odin ~]$ mpirun -np 1 printenv |grep foo
> foo=bar
> [tprins_at_odin ~]$ mpirun -np 1 -mca pls rsh printenv |grep foo
> So my question is which is the expected behavior?
> I don't think we can do anything about SLURM automatically forwarding the
> environment, but I think there should be a way to make rsh forward the
> environment. Perhaps add a flag to mpirun to do this?
> Thanks,
> Tim
> _______________________________________________
> devel mailing list
> devel_at_[hidden]