Hello,
Trying to understand some problems with "sacct " command.
I sent 10 jobs to slurm and I can see them all running in with squeue command.
Now, when I am running "sacct -j 398000" to check one of the jobs, I see two
problems:
1) Its take the sacct command about 3 minutes to return r
Hi,
I followed the steps described in [1]. However, srun still says --x11
is not a valid option. Should I restart slurm processes? That is not
mentioned in that document.
[root@rocks7 ~]# git clone https://github.com/hautreux/slurm-spank-x11
Cloning into 'slurm-spank-x11'...
remote: Counting obje
Hi Antonio,
if you don't care, which nodes are used, but want to ensure that only
uniform nodes are used, you could also use the topology/tree plugin,
where you define on "switch" for every node type and then use sbatch
--switches=1.
Best
Marcus
On 05/11/2018 05:49 PM, Antonio Lara wrote:
Thanks for responses.
Ian,
I will contact you.
Regards,
Mahmood
On Tue, May 15, 2018 at 12:15 PM, Marco Ehlert
wrote:
> Hi,
>
> if you are compiling slurm 17.11.5 the --x11 option will be in only if
> libssh2.so is installed before.
> Otherwise there will be no such option.
>
> Best,
> Marco
Hi,
if you are compiling slurm 17.11.5 the --x11 option will be in
only if libssh2.so is installed before.
Otherwise there will be no such option.
Best,
Marco
IT-Support
Max-Planck-Institute of Colloids Tel: +49-(0)331-567-9650
and InterfacesFax:
Hi,
in slurm 17.11.5 I just realized that slurmstepd tries to add the X11
magic cookie into .Xauthority inside root context in order to make x11
natively work.
The filesystem has to be configured to allow this. I did this
now, but I am wondering why it could not be done in the user's context
