I do see a diff between 2.0.1 and 2.0.2 that might have a related impact. The way we handled the MCA param that specifies the launch agent (ssh, rsh, or whatever) was modified, and I don’t think the change is correct. It basically says that we don’t look for qrsh unless the MCA param has been changed from the coded default, which means we are not detecting SGE by default.
Try setting "-mca plm_rsh_agent foo" on your cmd line - that will get past the test, and then we should auto-detect SGE again > On Feb 3, 2017, at 8:49 AM, Mark Dixon <m.c.di...@leeds.ac.uk> wrote: > > On Fri, 3 Feb 2017, Reuti wrote: > ... >> SGE on its own is not configured to use SSH? (I mean the entries in `qconf >> -sconf` for rsh_command resp. daemon). > ... > > Nope, everything left as the default: > > $ qconf -sconf | grep _command > qlogin_command builtin > rlogin_command builtin > rsh_command builtin > > I have 2.0.1 and 2.0.2 installed side by side. 2.0.1 is happy but 2.0.2 isn't. > > I'll start digging, but I'd appreciate hearing from any other SGE user who > had tried 2.0.2 and tell me if it had worked for them, please? :) > > Cheers, > > Mark > _______________________________________________ > users mailing list > users@lists.open-mpi.org > https://rfd.newmexicoconsortium.org/mailman/listinfo/users _______________________________________________ users mailing list users@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/users
