Sorry I didn't answer more completely before - a tad tied up today with network
problems :-/
Actually, both you and Michael pointed out the "flaw" in your own reasoning,
and hit the reason why we -don't- forward environment. It is obvious, for
example, that you don't want to forward HOSTNAME an
Ah - not good. It is clearly a programming error. I'll have to review the other
launchers and consult the others in the project to decide on the proper course
of action.
Thanks
On Nov 17, 2009, at 1:49 PM, David Singleton wrote:
>
> Hi Ralph,
>
> Now I'm in a quandry - if I show you that its
Hi Ralph,
Now I'm in a quandry - if I show you that its actually Open MPI that is
propagating the environment then you are likely to "fix it" and then tm
users will lose a nice feature. :-)
Can I suggest that "least surprise" would require that MPI tasks get
exactly the same environment/limits
On Nov 17, 2009, at 10:17 , Michael Sternberg wrote:
On Nov 17, 2009, at 9:10 , Ralph Castain wrote:
Not exactly. It completely depends on how Torque was setup - OMPI
isn't forwarding the environment. Torque is.
I actually tried compiling OMPI with the tm interface a couple of
versions back
Hi,
On Nov 17, 2009, at 9:10 , Ralph Castain wrote:
> Not exactly. It completely depends on how Torque was setup - OMPI isn't
> forwarding the environment. Torque is.
I actually tried compiling OMPI with the tm interface a couple of versions back
for both packages but ran into memory trouble, w
Not exactly. It completely depends on how Torque was setup - OMPI isn't
forwarding the environment. Torque is.
We made a design decision at the very beginning of the OMPI project not to
forward non-OMPI envars unless directed to do so by the user. I'm afraid I
disagree with Michael's claim that
I can see the difference - we built Open MPI with tm support. For some
reason, I thought mpirun fed its environment to orted (after orted is
launched) so orted can pass it on to MPI tasks. That should be portable
between different launch mechanisms. But it looks like tm launches
orted with the
Hi David,
Hmm, your demo is well-chosen and crystal-clear, yet the output is unexpected.
I do not see environment vars passed by default here:
login3$ qsub -l nodes=2:ppn=1 -I
qsub: waiting for job 34683.mds01 to start
qsub: job 34683.mds01 ready
n102$ mpirun -n 2 -machinefile $PBS_NODEFILE h
Hi Michael,
I'm not sure why you dont see Open MPI behaving like other MPI's w.r.t.
modules/environment on remote MPI tasks - we do.
xe:~ > qsub -q express -lnodes=2:ppn=8,walltime=10:00,vmem=2gb -I
qsub: waiting for job 376366.xepbs to start
qsub: job 376366.xepbs ready
[dbs900@x27 ~]$ module
Dear readers,
With OpenMPI, how would one go about requesting to load environment modules (of
the http://modules.sourceforge.net/ kind) on remote nodes, augmenting those
normally loaded there by shell dotfiles?
Background:
I run a RHEL-5/CentOS-5 cluster. I load a bunch of default modules t
10 matches
Mail list logo
