get over that fatal error without having to rebuild Slurm from
sources.
--
Davide Vanzo, PhD
Computer Scientist
BioHPC – Lyda Hill Dept. of Bioinformatics
UT Southwestern Medical Center
From: slurm-users On Behalf Of Robert
Kudyba
Sent: Wednesday, April 8, 2020 4:50 PM
To: Slurm User Community
the best route since it is clearly not a Slurm
issue, but a build configuration issue.
--
Davide Vanzo, PhD
Computer Scientist
BioHPC – Lyda Hill Dept. of Bioinformatics
UT Southwestern Medical Center
From: slurm-users On Behalf Of Robert
Kudyba
Sent: Wednesday, April 8, 2020 2:17 PM
To: Slurm
gured.
Apparently the Slurm build you are using has not be compiled against NVML and
as such it cannot use the autodetect functionality.
--
Davide Vanzo, PhD
Computer Scientist
BioHPC – Lyda Hill Dept. of Bioinformatics
UT Southwestern Medical Center
From: slurm-users On Behalf Of Robert
Kudyba
Sent: Tu
SelectType:
Changing this value can only be done by restarting the slurmctld daemon and
will result in the loss of all job information (running and pending) since the
job state save format used by each plugin is different.
--
Davide Vanzo, PhD
Computer Scientist
BioHPC – Lyda Hill Dept. of