Great. Yes, I forgot to mention that running or pending jobs can prevent deletion of this information. This makes scripting/automating all the sacctmgr functions somewhat difficult.
regards, Sam On Thu, Jan 3, 2019 at 10:18 AM Jianwen Wei <wei.jian...@gmail.com> wrote: > Thank you, Samuel. I've successfully delete the association with the > following command after the users' jobs completes. > > # sacctmgr delete user where name=clschf partition=k80 account=acct-clschf > > Best, > > Jianwen > > On Dec 29, 2018, at 11:50, Fulcomer, Samuel <samuel_fulco...@brown.edu> > wrote: > > ...right. An association isn't an "entity". You want to delete a "user" > where name=clschf partition=k80 account=acct-clschf . > > This won't entirely delete the user entity, only the record/association > matching the name/partition/account spec. > > The foundation of SLURM nomenclature has some unfortunate choices. > > On Fri, Dec 28, 2018 at 10:02 PM Jianwen Wei <wei.jian...@gmail.com> > wrote: > >> Hi, >> >> I want to purge resource limit set by an association before, say >> >> *[root@slurm1]~# sacctmgr show asso partition=k80 account=acct-clschf* >> * Cluster Account User Partition Share GrpJobs >> GrpTRES GrpSubmit GrpWall GrpTRESMins MaxJobs MaxTRES >> MaxTRESPerNode MaxSubmit MaxWall MaxTRESMins QOS >> Def QOS GrpTRESRunMin* >> *---------- ---------- ---------- ---------- --------- ------- >> ------------- --------- ----------- ------------- ------- ------------- >> -------------- --------- ----------- ------------- -------------------- >> --------- -------------* >> * sjtupi acct-clsc+ clschf k80 100 >> >> normal,qoslong,qosp+ normal* >> >> >> However, according to https://slurm.schedmd.com/sacctmgr.html "Add, >> modify, and delete should be done to a user, account or cluster entity. >> This will in-turn update the underlying associations." . Individual >> associations can not be deleted. Am I right? >> >> Best, >> >> Jianwen >> > >
