Are the older versions affected as well?
Best regards,
Taras
From: slurm-users on behalf of Tim
Wickberg
Sent: Thursday, October 12, 2023 00:01
To: slurm-annou...@schedmd.com ;
slurm-us...@schedmd.com
Subject: [slurm-users] Slurm versions 23.02.6 and 22.05.1
Russell-
Thanks for this, How do I assign a user to this level?
sacctmgr modify user set default=coordinator where default=something
--
---
Steven Hood
Linux Systems Admin
steven_h...@axiado.com
-Original Message-
From: Russell Jones
Reply-To: Slurm User Community List
To: Slurm Us
Slurm versions 23.02.6 and 22.05.10 are now available to address a
number of filesystem race conditions that could let an attacker take
control of an arbitrary file, or remove entire directories' contents
(CVE-2023-41914).
SchedMD customers were informed on September 27th and provided a patch
> On the automation part, it would be pretty easy to do regularly(daily?) stats
> of jobs for that period of time and dump them into an sql database.
> Then a select statement where cpu_efficiency is less than desired value and
> get the list of not so nice users on which you can apply whatever
I recall there was a built in tool named seff (slurm efficiency), not sure
if it is still maintained, but here is a link from my bookmark collection
related to some other slurm efficiency tool:
rse. princeton. edu/2020/01/monitoring-slurm-efficiency-with-reportseff/
On the automation part, it would
Diego Zuccato writes:
> IIUC Loris is looking for a method to do that automatically.
> Since there is a "used memory" metric, a corresponding "wasted memory"
> (or "wasted CPU") one with corresponding weights in priority
> calculations could be useful.
Yes, an automated solution is indeed what I
IIUC Loris is looking for a method to do that automatically.
Since there is a "used memory" metric, a corresponding "wasted memory"
(or "wasted CPU") one with corresponding weights in priority
calculations could be useful.
Diego
Il 11/10/2023 09:54, Williams, Gareth (IM&T, Black Mountain) ha
Hi Loris, You could add them to a naughty list (please use a better term...)
and apply a fixed commensurate priority penalty. That is simple (and can apply
to a range of unpreferred behaviour) and provides a clear motivation to change.
Could be done with QOS unless you already use that in a con
