Re: [OMPI users] Tight integration and interactive sessions with SGE

2008-11-13 Thread Scott Beardsley
Reuti wrote: What do you mean by "in the past" - you upgraded SGE from version x to version y? You can still source ///.1/environment. Sorry, you are right, this hasn't changed. By in the past I meant before we started using OMPI (and SGE with tight integration). There is nothing stopping

Re: [OMPI users] Tight integration and interactive sessions with SGE

2008-11-13 Thread Reuti
Am 13.11.2008 um 05:41 schrieb Scott Beardsley: Reuti wrote: qlogin will create a completely fresh bash, which is not aware of running under SGE. Although you could set the SGE_* variables by hand, it's easier to use an interactive session with: In the past we'd source some sge script and

Re: [OMPI users] Tight integration and interactive sessions with SGE

2008-11-12 Thread Scott Beardsley
Reuti wrote: qlogin will create a completely fresh bash, which is not aware of running under SGE. Although you could set the SGE_* variables by hand, it's easier to use an interactive session with: In the past we'd source some sge script and SLOTS, TMPDIR, etc were populated. $ qrsh -pe or

Re: [OMPI users] Tight integration and interactive sessions with SGE

2008-11-12 Thread Reuti
Scott, Am 13.11.2008 um 01:34 schrieb Scott Beardsley: I've been using OMPI 1.2.6 tightly integrated with Grid Engine for a bit now and it works great. However, I'm running into a problem running jobs from an interactive session (qlogin). I tried just doing "mpirun -np N /path/to/binary" w

[OMPI users] Tight integration and interactive sessions with SGE

2008-11-12 Thread Scott Beardsley
I've been using OMPI 1.2.6 tightly integrated with Grid Engine for a bit now and it works great. However, I'm running into a problem running jobs from an interactive session (qlogin). I tried just doing "mpirun -np N /path/to/binary" where N > # of cpus per node but OMPI will just oversubscribe