Fix issue with associations attached to a specific partition with no other association, and requesting a different partition.

Fixed issue where assoc_mgr cache wasn't always loaded correctly if the slurmdbd wasn't running when the slurmctld was started.

Fixed issue where if a system has unset messages to the dbd in 2.1 and upgrades to 2.2.  Messages are now processed correctly now.

    when job preemption is configured.

    job_submit and job_modify functions as an error and the user request should
    be treated as an error.

    into an array. Patch from Gerrit Renker, CSCS.

   "FairShare" and added more detail to the sshare man page.

Fix bug where if using the slurmdbd if a job wasn't able to start right away some accounting information may be lost.

    version 2.1. Bug introduced in version 2.2.0-pre10. Patch from Par
    Andersson, NSC.

    Patch from Gerrit Renker, CSCS.

    waiting for an allocation. This was broken in version 2.2.0.rc2.

BLUEGENE - make it so reset of boot counter happens only on state change and not when a new job comes along.

    in addition to "User"). Patch from Don Albert, BULL.

    than midplane counts.

sacctmgr now has smarts to figure out if a qos is a default qos when modifing a user/acct or removing a qos.

Made openssl not be required to build RPMs, it is not required anymore since munge is the default crypto plugin.

    salloc, sbatch and srun man pages. These options are defunct, Patch from
    Rod Schultz, Bull.

    managed. Substantially improves performance for large numbers of tasks.
    Adds support for SLURM_PMI_KVS_NO_DUP_KEYS environment variable. Patch
    from Hongjia Cao, NUDT.

    cancels a job while the node is not responding but slurmctld has not yet
    the node down. Patch from Hongjia Cao, NUDT.

    malloc function is interupted and called again. The malloc function is
    thread safe, but not reentrant.

xmalloc, which is not reentrant. original patch made in revision 21605

    state be NODE_FAIL rather than CANCELLED.

    tasks.

    a job and let the job's owner release it. The scontrol command of
    "hold <job_id>" when executed by a SLURM administrator can only be released
    by a SLURM administrator and not the job owner.

Apply rlimits right before execing the users task so to lower the risk of the task exiting because the slurmstepd ran over a limit (log file size, etc...)