Ticket 4154

Summary:	Add sacctmgr help/documentation for 'sacctmgr modify user .. set NewName'
Product:	Slurm	Reporter:	Josh Samuelson <josh>
Component:	User Commands	Assignee:	Tim Wickberg <tim>
Status:	RESOLVED FIXED	QA Contact:
Severity:	4 - Minor Issue
Priority:	---
Version:	17.02.6
Hardware:	Linux
OS:	Linux
Site:	University of Nebraska–Lincoln	Slinky Site:	---
Alineos Sites:	---	Atos/Eviden Sites:	---
Confidential Site:	---	Coreweave sites:	---
Cray Sites:	---	DS9 clusters:	---
Google sites:	---	HPCnow Sites:	---
HPE Sites:	---	IBM Sites:	---
NOAA SIte:	---	NoveTech Sites:	---
Nvidia HWinf-CS Sites:	---	OCF Sites:	---
Recursion Pharma Sites:	---	SFW Sites:	---
SNIC sites:	---	Tzag Elita Sites:	---
Linux Distro:	---	Machine Name:
CLE Version:		Version Fixed:	17.02.8 17.11.0-pre3
Target Release:	---	DevPrio:	---
Emory-Cloud Sites:	---
Attachments:	proposed patch

Description Josh Samuelson 2017-09-12 15:48:15 MDT

Created attachment 5206 [details]
proposed patch

Greetings,

Looking over the sacctmgr code on how qoslevel is parsed (unrelated to this bug entry), I came across the NewName option which isn't documented in the source/man/html.  Attached patch adds it.

FWIW, I also noticed in src/sacctmgr/sacctmgr.c:_process_command() a "rollup" command that calls acct_storage_g_roll_usage() which I assume eventually calls acct_storage_p_roll_usage(), documented in doc/html/accounting_storageplugins.shtml.  Should that also be documented in sacctmgr --help/man/shtml also?

Thanks,
-Josh

Comment 1 Tim Wickberg 2017-09-12 21:41:09 MDT

Commit d08f34f2793d9, and it'll be in 17.02.8 when released. Thank you for the patch!

The rollup command is intentionally not documented - it's there if extenuating circumstances require such an intervention, but it's not to be used lightly.