This patch contains corrections for spelling errors in the code and
improvements for some man pages. Patch from Gennaro Oliva.

Patch by Stephen Trofinoff, CSCS.

Change the logging of a job step create failure due to SlurmctldProlog
running from info() to debug() since this can be due to a race condition.

Do not attempt to run HeathCheckProgram on powered down nodes. Patch from
Ramiro Alba, Centre Tecnològic de Tranferència de Calor, Spain.

This reverts https://github.com/hautreux/slurm/commit/35075c10995f4e83d0104662f147cd7b413d25f4
My version of RPM doesn't seem to understand the "replace"
parameter for %config, so rpm builds bomb out with
    Invalid %config token: replace
    Invalid %config token: replace

I think the default for %config is to not replace config
files, so I'm not sure this commit is needed. Since the
release agents are not really config files, but need to
be tightly coupled to the release of task/cgroup and
proctrack/cgroup, I would say the release agents should
be moved under /usr/libexec/slurm

At the very least, this commit needs to be reverted before slurm-2.3.1
in order to allow rpms to be built.

Thanks,
Mark Grondona

Report correct job "Reason" if needed nodes are DOWN, DRAINED, or
NOT_RESPONDING, "Resources" rather than "PartitionNodeLimit".

plugins in the slurmd.

    value for jobs.

Cgroup plugins update

For a long time configure has modified the SLURM Release number
as set in META by stripping off everything before the last '.'
when building the SLURM_VERSION_STRING. This was done so that a
release number of 0.pre1 would become just 'pre1' in the version
string printed by SLURM commands. (e.g. slurm-2.3.0-0.pre1 becomes
slurm-2.3.0-pre1 in sinfo --version).

In attempting to create a new version 2.3.0-2.x of SLURM (branched
from 2.3.0-2), it was found that this method is overzealous, and
results in a version string of just "2.3.0-1" instead of the expected
"2.3.0-2.1". Since the intent of the sed command is only to remove
'0.' from prereleases, this patch makes that explicit, so that
non-prerelease versions branched of tagged SLURM releases keep the
original Release number in the version string.

Cray - Fix for srun.pl parsing to avoid adding spaces between option and
argument (e.g. "-N2" parsed properly without changing to "-N 2").

The addition of the default slurm cg with the cpuset subsystem was
incomplete preventing from having a working solution. The contents
of cpuset.cpus and cpuset.mems were not replicated from the parent
resulting in "No space left on device" errors when trying to add
tasks to the step cg.

When doing modifications on the cgroup internals of SLURM it can be
necessary to modify the associated release agents. It is necessary
for the SLURM RPM to automatically replace these agents.

Conflicts:
	etc/cgroup.release_common.example
	src/plugins/task/cgroup/task_cgroup_memory.c

In order to distinguish between slurm related cg and system related cg,
ensure that all slurm related cgroup directories are created under a
single directory. This directory is slurm or slurm_nodename in case of
multiple-slurmd usage.

Update cgroup.conf(5) with documentation for new parameters
CgroupMountpoint, MinRAMSpace, MaxRAMPercent and MaxSwapPercent.
Also include information about handling of AllowedRAMSpace when
memory is not explicitly allocated by SLURM.

Add the amount of memory allocated by slurm to the job or step
to the debug message in memcg_initialize(). Also, change the
message from debug to info, so that a user can see the information
by using --slurmd-debug=1.

For debugging purposes, add a debug level message with some values
of interest just after task_cgroup_memory has initialized.

Add a new configuration parameter MinRAMSpace which sets a lower bound on
memory.limit_in_bytes and memory.memsw.limit_in_bytes . This is required in
case an administrator or user sets an absurdly low value for memory limit,
potentially causing the slurmstepd to be terminated by the OOM killer.

MinRAMSpace is set in MB of RAM and is 30 by default. (An arbitrarily
chosen value)

The use of whole percent values for cgroup.conf parameters such
as AllowedRAMSpace, MaxRAMPercent, AllowedSwapSpace and MaxSwapPercent
may be too coarse grained on systems with large amounts of memory.
(e.g. 1% of 64G is over 650MB).

This patch allows these percentage values to be arbitrary floating
point numbers to allow finer grained tuning of these limits and
parameters.