On 11/19/18 4:51 PM, Mahmood Naderan wrote:
> With and without --x11, I am not able to see xclock on a compute node.
>
> [mahmood@rocks7 ~]$ srun --x11 --nodelist=compute-0-3 -n 1 -c 6
> --mem=8G -A y8 -p RUBY xclock
> srun: error: Cannot forward to local display. Can only use X11
> forwarding w
Hi,
I gave a presentation at SC in the slurm booth on some slurm job efficiency
tools, and web app that we developed. I figured that maybe others in this group
could be interested too. If you'd like to see the short presentation, and the
tools, and links to them, please see this presentation:
Excuse me, the last email was mistakenly sent.
The ssh config seems to be fine
[root@rocks7 ~]# grep X11 /etc/ssh/sshd_config
X11Forwarding yes
X11UseLocalhost no
Werner,
I am running that command on TTY. As you can see, I can run xclock while
sshing to the node
[mahmood@rocks7 ~]$ ssh -Y
With and without --x11, I am not able to see xclock on a compute node.
[mahmood@rocks7 ~]$ srun --x11 --nodelist=compute-0-3 -n 1 -c 6 --mem=8G -A
y8 -p RUBY xclock
srun: error: Cannot forward to local display. Can only use X11 forwarding
with network displays.
[mahmood@rocks7 ~]$ srun --nodelist
Paul,
Thanks for the response, I tested and activated LLN on a per partition
basis in our cluster. Works exactly as described and satisfied my need
perfectly. Thanks!
--
Aravindh Sampathkumar
aravi...@fastmail.com
On Thu, Nov 15, 2018, at 3:25 PM, Paul Edmon wrote:
> I recommend the LLN op
On Sunday, 18 November 2018 4:24:08 AM AEDT Mahmood Naderan wrote:
> >What does this command say?
> >
> >scontrol show config | fgrep PrologFlags
>
> [root@rocks7 ~]# scontrol show config | fgrep PrologFlags
> PrologFlags = Alloc,Contain,X11
>
> That means x11 has been compiled in
Hello,
two things; you don't actually seem to have the '--x11' flag on your
srun command? I.e. does 'srun --x11 --nodelist=compute-0-5 -n 1 -c 6
--mem=8G -A y8 -p RUBY xclock' get you any further?
I had some trouble getting the inbuild X forwarding to work, which had
to do with hostnames & xau
