Yeah. Sorry for that. Wasn’t even a wrong cc. Was wanting to send this to
someone who keeps our contacts list up to date … but hit reply instead of
forward.
> Am 20.11.2019 um 14:24 schrieb Daniel Povey :
>
> The accidental cc!
>
> On Wed, Nov 20, 2019 at 9:22 PM Friedrich Ferstl
The accidental cc!
On Wed, Nov 20, 2019 at 9:22 PM Friedrich Ferstl wrote:
> This person was at the Smithsonian until very recently and shows up in
> our support records but he is now CFA/Harvard, apparently, using open
> source.
>
>
> Am 19.11.2019 um 23:41 schrieb Korzennik, Sylvain <
>
This person was at the Smithsonian until very recently and shows up in our
support records but he is now CFA/Harvard, apparently, using open source.
> Am 19.11.2019 um 23:41 schrieb Korzennik, Sylvain
> :
>
> While qrsh and qlogin works fine, qsh fails on
> % qsh
> Your job 2657108
Thanks Reuti,
Since qsh relies on a direct connection it will always fails and
should be removed (or forgotten). qrsh xterm fails on our system b/c
only qlogin_command (qconf -sconf) is set to use ssh -X, but qlogin works
fine to open an interaction session, and at that session prompt xterm (or
Hi,
Am 19.11.2019 um 23:41 schrieb Korzennik, Sylvain:
> While qrsh and qlogin works fine, qsh fails on
> % qsh
`qsh` uses the old-style invocation only. I.e. it will make a direct connection
to the submission host, where access has to be granted by `xhost +` beforehand
(and open ports 6000
While qrsh and qlogin works fine, qsh fails on
% qsh
Your job 2657108 ("INTERACTIVE") has been submitted
waiting for interactive job to be scheduled ...
Could not start interactive job (could be some network/firewall related
problem)
from the same prompt/login node, I can
% ssh -X compute-64-16
