Re: [SGE-discuss] Tight integration with qrsh

2017-02-27 Thread Reuti
Am 27.02.2017 um 23:18 schrieb Raymond Norris: > Thanks. Running > > smpd -d 0 & > > did the trick. Although I needed to > > sleep 5 > > afterwards because I was getting to mpiexec to quickly. Yes, therefore I had the loop in the startmpich2.sh script to use an async `qrsh` to the nod

Re: [SGE-discuss] Tight integration with qrsh

2017-02-27 Thread Raymond Norris
Thanks. Running smpd -d 0 & did the trick. Although I needed to sleep 5 afterwards because I was getting to mpiexec to quickly. Raymond > Hi, > > Am 17.02.2017 um 21:55 schrieb Raymond Norris: > > >> Hi, > >> > >>> Am 17.02.2017 um 18:54 schrieb Raymond Norris > >> : > >>> > >>> Hi,

Re: [SGE-discuss] Tight integration with qrsh

2017-02-17 Thread Reuti
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Am 17.02.2017 um 21:55 schrieb Raymond Norris: >> Hi, >> >>> Am 17.02.2017 um 18:54 schrieb Raymond Norris >> : >>> >>> Hi, >>> >>> I'm using SoGE 8.1.9. >>> >>> When we setup our jobs to run with loose integration and SSH, things work >> fin

Re: [SGE-discuss] Tight integration with qrsh

2017-02-17 Thread Raymond Norris
> Hi, > > > Am 17.02.2017 um 18:54 schrieb Raymond Norris > : > > > > Hi, > > > > I'm using SoGE 8.1.9. > > > > When we setup our jobs to run with loose integration and SSH, things work > fine. I'm now trying to configure this with tight integration and qrsh. > Sans a > dozen or so ports, every

Re: [SGE-discuss] Tight integration with qrsh

2017-02-17 Thread Simão Afonso
You can run the qrsh tight integration with SSH, just alter the rsh_command and rsh_daemon configuration variables. I don't remember where I read this (probably the official documentation), but here's the relevant section of my "qconf -mconf": qlogin_command /opt/sge/util/resourc