It doesn’t affect the use case of connecting via srun afterwards as no new job
is submitted so the job_submit.lua logic is never called.
$ srun --pty /bin/bash
srun: error: submit_job: ERROR: interactive jobs are not allowed in the CPU or
GPU partitions. Use the interactive partition
srun: error
...that would interfere with users 'logging in' to a job to check on it
though, wouldn't it? I mean we do have pam_slurm_adopt configured but I
still tell people it's preferable to use 'srun --jobid= --pty
/bin/bash' to check what a specific job is doing as pam_slurm_adopt
doesn't seem to i
Hi Peter,
as Rémi said, the way to do this in Slurm is via a job submit plugin. For
example in our job_submit.lua we have
if (job_desc.partition == "cpu" or job_desc.partition == "gpu") and
job_desc.qos ~= "admin" then
if job_desc.script == nil or job_desc.script == '' then
slurm.l
Hi Peter,
Le lundi 14 février 2022 à 18:37, Peter Schmidt a écrit
:
> slurm newbie here, converting from pbspro. In pbspro there is the capability
> of limiting interactive jobs (i.e srun) to a specific queue (i.e partition).
Note that in Slurm, srun and interactive jobs are not the same thin
slurm newbie here, converting from pbspro. In pbspro there is the
capability of limiting interactive jobs (i.e srun) to a specific queue
(i.e partition).
I'm wondering if a similar restriction can be applied in slurm?
Thanks!
