Ticket 7203

Summary:	Inconsistent usage of "DefCpusPerGPU" vs. "DefCpuPerGPU"
Product:	Slurm	Reporter:	bugert
Component:	Documentation	Assignee:	Jacob Jenson <jacob>
Status:	RESOLVED INVALID	QA Contact:
Severity:	6 - No support contract
Priority:	---
Version:	19.05.x
Hardware:	Linux
OS:	Linux
Site:	-Other-	Alineos Sites:	---
Atos/Eviden Sites:	---	Confidential Site:	---
Coreweave sites:	---	Cray Sites:	---
DS9 clusters:	---	HPCnow Sites:	---
HPE Sites:	---	IBM Sites:	---
NOAA SIte:	---	OCF Sites:	---
Recursion Pharma Sites:	---	SFW Sites:	---
SNIC sites:	---	Linux Distro:	---
Machine Name:		CLE Version:
Version Fixed:		Target Release:	---
DevPrio:	---	Emory-Cloud Sites:	---

Description bugert 2019-06-07 09:40:13 MDT

Hi,

I just spent an hour trying to figure out why slurm 19.05 rejects our slurm.conf which uses the new "DefCpusPerGPU" parameter. Inspection of the config parser code revealed that slurm expects the parameter to be called "DefCpuPerGPU".

The wrongly spelled parameter is reported in many cases:

- in the slurm.conf documentation: https://github.com/SchedMD/slurm/blob/master/doc/man/man5/slurm.conf.5
- in the 19.05 release notes
- in the slides from SLUG 2018: https://slurm.schedmd.com/SLUG18/cons_tres.pdf

The scontrol documentation uses the correct spelling: https://github.com/SchedMD/slurm/blob/master/doc/man/man1/scontrol.1

Best regards,
Michael Bugert