to the stepd where we will use it with the different plugins to gather
TRES usage.

What it does here currently is sends the assoc_mgr_tres_list to the
slurmd who then creates the assoc_mgr end there.

to avoid freeing it on accident.

messages other than just rc messages.

It isn't used quite yet, but will be in the next commit!

code copied from slurmdbd_defs.c so we can use it elsewhere.

This way we can put more on here as startup was only a bool anyway.

in the form of assoc_mgr_post_tres_list

Bug 2872

Not sure if this could be done a different way.  At the moment I
wouldn't mind making a common structure to get the read and writes. Or
perhaps make use of a different array or such.

In the end this might be the best way to do it, but it isn't clear at
the moment since the num_* isn't sent to the database in any fashion.

    Bug 2782

This will most likely be reverted as well since we plan on moving the
Usage TRES to dynamic.

Bug 2782

Bug 2782

Not sure if this could be done a different way.  At the moment I
wouldn't mind making a filesystem specific structure to pass in. Or
perhaps make use of a different array or such.

In the end this might be the best way to do it, but it isn't clear at
the moment since the num_* isn't sent to the database in any fashion.

Bug 2782

This will most likely be reverted as well since we plan on moving the
Usage TRES to dynamic.

Bug 2782

At the moment I am wondering if this is needed or not.  Perhaps we might
want to revert this.

Bug 2782

Bug 2782

Bug 2782

Bug 2782

TRES.  This will hopefully be reverted in the future when TRES
information is returned from the slurmd.

Bug 2782

Bug 2782

char * nodelist.

Bug 2782

Bug 2782

Bug 2782

the future.

Bug 2782

to get ready for additions.

Hopefully no code change

Bug 2782

Bug 2782

Bug 2782

Bug 2782

Log the option is not supported using info() message:
$ sbatch -I tmp
sbatch: --immediate option is not supported for the sbatch command, ignored
Submitted batch job 1234

'sacctmgr show accounts withassoc cluster=x' now behaves like 'show users'
displaying always all the accounts on the enterprise. Non-matching filtered
account is now just displayed without associations.

Bug 4804

When Cray NHC is stuck for a job for more than 300 seconds and a
reconfigure is issued, job resources will be released in order to
not keep all the job nodes allocated when there's no reason to.
If then NHC finishes, resources will be released again causing memory
under-allocated errors.

This patch avoids releasing resources more than one time.

Bug 4801