Actually, I solved the issue by observing that the user had created a
file "~/.vnc/xstartup*.sh*" while it should have been "~/.vnc/xstartup"
at least, simply removing the extension and vncserver starts
successfully, even in a srun !
Best;
Jeremy.
On 15/05/2021 14:02, Jeremy Fix wrote:
> Hello
Durai Arasan writes:
> Is there a way of improving this situation? E.g. by not blocking IDLE nodes
> with jobs that only use a fraction of the 8 GPUs? Why are single GPU jobs
> not scheduled to fill already MIXED nodes before using IDLE ones?
>
> What parameters/configuration need to be adjusted
Il 17/05/21 09:25, Ole Holm Nielsen ha scritto:
I hope that someone on the list can help you build Debian packages.
The problem is not just rebuilding Slurm: if I rebuild Slurm, I have to
rebuild OpenMPI, OpenIB and a alot of other stuff that I don't know with
the needed detail.
When you fi
On 5/17/21 8:59 AM, Diego Zuccato wrote:
Il 15/05/21 00:43, Christopher Samuel ha scritto:
It just doesn't recognize 'ALL'. It works if I specify the resources.
That's odd, what does this say?
sreport --version
slurm-wlm 18.08.5-2
That's the package from Debian stable (we don't have the manpo
Il 15/05/21 00:43, Christopher Samuel ha scritto:
It just doesn't recognize 'ALL'. It works if I specify the resources.
That's odd, what does this say?
sreport --version
slurm-wlm 18.08.5-2
That's the package from Debian stable (we don't have the manpower to
handle manually-compiled packages)
