cause potential deadlock when/if TRES changed in the database and the
slurmctld wasn't made aware of the change.  This would be very rare.

The lock was originally there to keep new jobs from grabbing the assoc
information.  If the lock was done afterwards the worst case is we get the new
information.

It was determined we didn't need the write locks on the job and no locks were
needed on the node either.

Doing these different locked beforehand would create a window where you could
get a config write lock

Bug 3507.

This will be triggered after either a burst buffer job_begin function
  or select plugin job_begin function fails. Without this change, the
  "squeue -i" and "scontrol show job" commands can report old job
  state information.
bug 3504

Burst_buffer/cray - Prevent slurmctld daemon abort if "paths" operation
    fails. Now job will be held.
bug 3504

bug 3182

bug 3473

reason to 32 chars.

Mention how to enable systemd service files.

MUNGE is required, don't even mention auth/none which is only for testing.

"srun --core" does not exist.

Parallel debugger support - does not belong in quickstart.

Testing section - does not belong in quickstart.

Set to inline and leave the font color and background alone.

bug 3498