On 1/31/24 09:02, Bjørn-Helge Mevik via slurm-users wrote:
This isn't answering your question, but I strongly suggest you build
Slurm from source. You can use the provided slurm.spec file to make
rpms (we do) or use "configure + make". Apart from being able to
upgrade whenever a new version is
I agree with Bjørn to build it from source to have more control. We do
it with tarballs like schedmd suggests so we can also easily switch
between versions without deleting/installing rpms/debs.
On 31/01/2024 09:02, Bjørn-Helge Mevik via slurm-users wrote:
This isn't answering your question, b
My impression is, that there are multiple challenges why it's not easy
to create good-for-all recent slurm RPM:
- NVML dependency - different sites use different NVML lib version with
varying update cycle
- pmi* deps - some sites (like mine) is using only one reasonable recent
openpmix, I know
This isn't answering your question, but I strongly suggest you build
Slurm from source. You can use the provided slurm.spec file to make
rpms (we do) or use "configure + make". Apart from being able to
upgrade whenever a new version is out (especially important for
security!), you can tailor the
