[GE users] qrsh_starter/shepherd problems?
harry.mangalam at uci.edu
Tue Nov 25 20:57:15 GMT 2008
Thanks again Reuti,
Your links are tasty as ever. And the wrapper I thought I had seen
was on the 1st link and yes, it does work as advertised.
Now both qrsh and qlogin are working as expected. I'll just hide or
link qsh to prevent its use in the future.
On Tuesday 25 November 2008, reuti wrote:
> Am 25.11.2008 um 18:44 schrieb Harry Mangalam:
> > I'm struggling get the various qrsh, qsh, qlogin commands working
> > as well. Given the bug that Harald cites, what is the
> > recommended way to set up the global config.
> > I was trying to use ssh for everything:
> > qlogin_command /usr/bin/ssh
> > qlogin_daemon /usr/sbin/sshd -i
> > rlogin_command /usr/bin/ssh -Y
> > rlogin_daemon /usr/sbin/sshd -i
> > rsh_command /usr/bin/ssh -Y
> > rsh_daemon /usr/sbin/sshd -i
> > but under this config:
> > - qrsh works well (user will be connected to an execution node
> > and be able to view X11 apps - critical to our usage model),
> > - qsh doesn't work:
> > $ qsh
> > Your job 57 ("INTERACTIVE") has been submitted
> > waiting for interactive job to be scheduled ...
> > Could not start interactive job.
> This will not work, as it's using a plain TCP connection and you
> would need "xhosts +" and switch the firewall off on ports 6000+.
> Nowadays this is not recommended.
> But you can use with the above ssh setup: qrsh xterm
> -- Reuti
Harry Mangalam - Research Computing, NACS, E2148, Engineering Gateway,
UC Irvine 92697 949 824-0084(o), 949 285-4487(c)
Good judgment comes from experience;
Experience comes from bad judgment. [F. Brooks.]
To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].
More information about the gridengine-users