Hi Em,
this was somehow mentioned in the 20.11.0 Release Notes:
https://github.com/SchedMD/slurm/blob/slurm-20-11-0-1/RELEASE_NOTES
-- By default a step started with srun will get --exclusive behavior meaning
no other parallel step will be allowed to run on the same resources at
the same
Hi, Juergen --
This is really useful information -- thanks for the pointer, and for taking
the time to share!
And, Jacob -- can you point us to any primary documentation based on
Juergen's observation that the change took place with v20.11?
With the emphasis on salloc, I find in the examples:
>
Oh hey this is fun, thanks for sharing. I hadn't seen this, but it works as
advertised.
Jason
On Thu, Nov 3, 2022 at 12:31 AM Christopher Samuel
wrote:
> On 11/2/22 4:45 pm, Juergen Salk wrote:
>
> > However, instead of using `srun --pty bash´ for launching interactive
> jobs, it
> > is now rec
