Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Open MPI User's mailing list

Subject: Re: [OMPI users] ompi + bash + GE + modules
From: Mark Suhovecky (suhovecky_at_[hidden])
Date: 2012-01-12 10:05:27


I'm working with Univa support as well.

I started out debugging this with pretty poor grasp of where in the software flow the problem
might be. Like most sysadmins, I belong to many community lists, and find them to be of tremendous
help in running problems down. They certainly have been in this case- I've posted to the modules-interest
sourcefourge group as well.

I choose to use all the resources open to me, including community user forums and paid support, Using
a commercial product's support should not preclude one from using other tools as well.


Mark Suhovecky
HPC System Administrator
Center for Research Computing
University of Notre Dame
From: users-bounces_at_[hidden] [users-bounces_at_[hidden]] On Behalf Of Dave Love [d.love_at_[hidden]]
Sent: Thursday, January 12, 2012 8:40 AM
To: users_at_[hidden]
Subject: Re: [OMPI users] ompi + bash + GE + modules

Surely this should be on the gridengine list -- and it's in recent
archives -- but there's some ob-openmpi below. Can Notre Dame not get
the support they've paid Univa for?

Reuti <reuti_at_[hidden]> writes:

> SGE 6.2u5 can't handle multi line environment variables or functions,
> it was fixed in 6.2u6 which isn't free.

[It's not listed for 6.2u6.] For what it's worth, my fix for Sun's fix

> Do you use -V while submitting the job? Just ignore the error or look
> into Son of Gridengine which fixed it too.

Of course
you can always avoid the issue by not using `export -f', which isn't in
the modules version we have. I default -V in sge_request and load
the open-mpi module in the job submission session. I don't
fin whatever problems it causes, and it works for binaries like
  qsub -b y ... mpirun ...
However, the folkloristic examples here typically load the module stuff
in the job script.

> If you can avoid -V, then it could be defined in any of the .profile
> or alike if you use -l as suggested. You could even define a
> started_method in SGE to define it for all users by default and avoid
> to use -V:
> #!/bin/sh
> module() { }
> export -f module
> exec "${@}"

That won't work for example if someone is tasteless enough to submit csh.

users mailing list