Also simplify this xstrfmtcat() into an xstrcat() call while here.

Bug 5828.

Leads to false-positive warnings about settings being too low when
they're actually fine. E.g., if innodb_buffer_pool_size is over 2GB
the warning would have been printed in error.

Bug 5661.

Bug 5594.

You should not make RPC calls within MailProg (or anything else
fork()+exec()'d from slurmctld), so use the environment variable that
is now exposed instead.

Bug 5443.

smail currently uses 'scontrol show config' to get this data; making RPC
calls within programs fork()+exec()'d from slurmctld is best avoided as
it amplifies RPC load on the controller.

Bug 5443.

Add info to man page as well.

Bug 4961.

Bug 5724

Bug 5708

Continuation of 06582da8 (17.11.9)

Poll was timing out too quickly due to an incorrect conversion of
MessageTimeout. Added a multiplier so timeout reflects the correct
millisecond value.

Bug 5553

Since sacct exits the program when it finds unknown parameters, the
debug2() statements should be escalated to error() statements.
The first debug2() even had "Error: " in it.
Get rid of extra newline.

Bug 5421

Bug 5743.

Co-authored-by: Dominik Bartkiewicz <bart@schedmd.com>

The format for this field is "<inst>:<svc_id>:<comp_id>"; if inst or svc_id
are unset then they're blank, and the parsing code had assumed they would
always be blank as the systems slurmsmwd were developed on never used them.

Bug 5411.

Prevents job priorities from being lowered to 0 or from underflowing.

Bug 5165

Bug 5231

Change slurmctld/controller.c's purge_thread_lock from static to
global extern, so the mutex can be used in slurmctld/job_mgr.c

slurm_cond_signal() needs to always be wrapped in the same mutex as
slurm_cond_[timed]wait(), or else there is a possibility that
slurm_cond_signal() will trigger before slurm_cond_[timed]wait()
is even listening, most likely causing a deadlock.

initialize old fairshare association pointer correctly.

Bug 5744

Bug 5458

Bug 5403

Bug 5750

Bug 5748

Bug 5775

Bug 5544

Bug 5544

Bug 5613

Now slurmctld will fatal if the two incompatible memory enforcement mechanisms
are configured at the same time (JobAcctGather + task/cgroup). Also, a new info
message in slurmctld startup will indicate if there are not any configured
mechanism.

Bug 5479

Bug 5762

bug 5669

by integers.

We understand this reverts bc7b91cd, but in all our testing we have
been unsuccessful finding what that commit actually does.

Bug 5711
Bug 5746

This reverts commit 204da0b6.

# Conflicts:
#	NEWS

So this takes us back to 204da0b6.

See bug 5746

distribution.

Bug 5706

This reverts commit 450cd6c8.

Bug 5711

This will be re-reverted in 19.05 with other code changes we didn't feel
comfortable dealing with in 18.08.

Bug 5702

The backup slurmctld can end up without an agent thread if
read_slurm_conf() takes too long to complete. Forcing the agent_init()
here again ensures it is restarted if not currently running.

This was fixed upstream in c1a537db.

Bug 5633.

Functionality is still available if required, but has been deprecated
since 17.11, and has been removed on master before 19.05.

Un-document is now lest people start trying to use it.

support.

Bug 4871

is removed from the system.

Bug 5665

burst buffer.

Bug 5665