Regardless of the reason, if I had to modify anything like that in the db, I wouldn’t go the SQL route.
I would sacctmgr dump to a file. Modify the file, and sacctmgr load the file. Let the slurmdbd handle the SQL stuff.
While I’m at it, I’d do it in a git, for good accounting.
But as stated - it might not be necessary at all. Just my 2 cents.
Sent from my iPhone
On 4 Jun 2025, at 17:11, Burian, John via slurm-users slurm-users@lists.schedmd.com wrote:
All,
For reasons I won’t go into, we find we need to change the POSIX group names for all of our users. My understanding is that in the absence of an --account option, sbatch/salloc assumes the account is the user’s primary POSIX group.
So, to change group names, we’ll need to change the account names on all the associations in sacctmgr. And ideally, we would change account names in accounting records so we don’t lose accounting history.
One is tempted to get into the Slurm DB and start running SQL updates. Is that path too fraught with peril to consider? Or should I just recreate the associations with the new names and take my lumps on the accounting history?
John
-- slurm-users mailing list -- slurm-users@lists.schedmd.com To unsubscribe send an email to slurm-users-leave@lists.schedmd.com