Hi Guillaume,
as Rob it already mentioned, this could maybe a way for you (partition
just created temporarily online for testing). You could also add your
MaxTRES=node=1 for more restrictions. We do something similar with QOS
to restrict the number of CPU's for user in certain partitions.
, without the InteractiveStepOptions parameter.
JLS
On Thu, Sep 5, 2024 at 9:53 AM Carsten Beyer via slurm-users
wrote:
Hi Loris,
we use SLURM 23.02.7 (Production) and 23.11.1 (Testsystem). Our
config
contains a second parameter InteractiveStepOptions in slurm.conf
Hi Loris,
we use SLURM 23.02.7 (Production) and 23.11.1 (Testsystem). Our config
contains a second parameter InteractiveStepOptions in slurm.conf:
InteractiveStepOptions="--interactive --preserve-env --pty $SHELL -l"
LaunchParameters=enable_nss_slurm,use_interactive_step
That works fine for u
Hi Christine,
we don't use AllowGroups but have AllowAccounts, which is not working
anymore as expected in version 23.02.x. We tried also with
EnforcePartLimits.
I can see that our slurmctld consumes each day approx. 1g more memory.
Our current version is 23.02.7 which comes from ATOS/EVIDEN
Hi Josef,
we use ClusterCockpit for that purpose. Users could monitor their
running jobs or have a look for finished jobs.
https://www.clustercockpit.org/
Best Regards,
Carsten
--
Carsten Beyer
Abteilung Systeme
Deutsches Klimarechenzentrum GmbH (DKRZ)
Bundesstraße 45a * D-20146 Hamburg * G