This whole process could probably be done better by keeping track of
old values and new values and only calling one function instead of a
pre and post function, but that can probably wait for future generations
of the code as it works now and is probably adequate for the time being.

Bug 2352

Consistantly use American English for
existant -> existent
assocation -> association

Correct some typos, and one grammatical mistake.

BurstBuffer/cray - Defer job cancellation or time limit while "pre-run"
    operation in progress to avoid inconsistent state due to multiple calls
    to job termination functions.
bug 2454

Otherwise call fclose(NULL) iff the ClusterName is not set and the
clustername file does not exist. Should not happen in production.

Coverity #67041.

a new account and making it a default all at once.

Bug 2428

Match acct_gather_energy/rapl plugin. Bug 2397.

Control whether the scheduler will continue to try to run jobs in
a partition if a higher priority job is stuck due to an association
limit.

Can cause starvation for larger jobs, but will improve throughput and
utilization for systems that have extensively divvyed up their resources
through association/QOS limits.

Bug 2388 and 2452.

Bug 2453

This should have no effect, but is a belt-and-suspenders approach
  to checking node state.

have been selected set the time limit appropriately if the job didn't
request one.

If the partition has no DefaultTime setting, and no time_limit was given
for the job, job_ptr->time_limit == NO_VAL.

With AccountingStorageEnforce=safe this will prevent jobs from ever
starting if the association has any limit set for CPUMins.
(NO_VAL * cpus is a very large number, but if no time_limit is given
anywhere that is what they get :))

Bug 2388.

a parsing option.

Dynamically set columns widths based on largest number in column.

accounting.

AccountUtilizationByUser report a parent could potentially (correctly)
be larger than the sum of it's children because of the way
accounting for reservations work.

was given with just an =, i.e. users= without specifying any users after
the =.

period.  This would only hit you if you rerolled a 15.08 prior to this
commit.

Don't expand on the format or arguments, these have changed in
16.05 already and may vary further with BB/generic support.

These are very unlikely to ever occur, but this helps harden the code.

Compare the saved clustername to slurmctld's, if there's a mismatch prevent
slurmctld from starting to avoid corruption from separate clusters attempting
to share a single state directory.

Bug 2433.

Non-GLIBC LIBC's are strict about when these functions are visible.

Bug 2427

Reproduced with:
sacctmgr show user withassoc user= user=<username>