I certainly missed that. The documentation seems to still have the --x11 flag in it (below).
Is there another way to use x11 via sbatch with similar behavior? This has affected some users and I'd like to find a similar simple solution. The man page (19.05.0/share/man/man1/sbatch.1) and online (https://slurm.schedmd.com/sbatch.html) read: --x11[=<all|batch|first|last>] Sets up X11 forwarding on all, batch host, first or last node(s) of the allocation. This option is only enabled if Slurm was com‐ piled with X11 support and PrologFlags=x11 is defined in the slurm.conf. Default is batch. Thanks, -Dean Hidas On 5/29/19, 7:00 PM, "slurm-users on behalf of Sean Crosby" <slurm-users-boun...@lists.schedmd.com on behalf of scro...@unimelb.edu.au> wrote: Hi Dean, On Thu, 30 May 2019 at 07:30, Hidas, Dean <dhi...@bnl.gov> wrote: Is there any idea what I might have missed? The release notes say that the new X11 code will not work with sbatch - https://github.com/SchedMD/slurm/blob/master/RELEASE_NOTES NOTE: The X11 forwarding code has been revamped, and no longer relies on libssh2 to function. However, support for --x11 alongside sbatch has been removed, as the new forwarding code relies on the allocating salloc or srun command to process the forwarding. Sean -- Sean Crosby Senior DevOpsHPC Engineer and HPC Team Lead | Research Platform Services Research Computing | CoEPP | School of Physics University of Melbourne
