Keep log message string on single line

i.e. Centos7

Test was always leaving around a file named "slurm.conf.orig".
Now delete the file on test success.

bug 6878

Previous logic would wait up to 5 seconds. New logic will extend
the time limit up to half of MessageTimeout (minimum value still
5 seconds).

Previous logic lacked locks on global data structure.
Also initialized some variables to NULL before use.

Previous logic placement would result in sending NULL for
topology information. Moved buffer build later in the logic.

bug 5667

# Conflicts:
#	src/slurmctld/job_mgr.c
#	src/slurmctld/proc_req.c
#	src/slurmd/slurmd/req.c
#	testsuite/expect/test21.39

We will store the pid of running scripts on a list in order to kill them
when slurmctld is shutting down. This will make the thread running the script
to end, so we will join this thread too, but only during a specified timeout,
because if the pid forked by the caller thread is stuck in IO, slurmctld will
be stuck too.

We also need to diferentiate when a sigkill is send by a human or OOM, from
the one send by slurmctld when killing it, so the one way wil be to set
ctld_script_rec_t jobid to -1 when we are killing the process.

Work to do includes adding this logic to the burst_buffer functions which use
the run_command() function.

Work to do also may need to add locks for accessing ctld_script_rec_t records.

Bug 5913

Now that the pid is no longer an argument, the name doesn't make sense.
Change to container_g_join() to reflect the underlying functionality.

Bug 6567.

Removal of this argument forces the use of this function call only for
adding the calling process - and not any other process - to the job
container. This is needed for an in-development job container
plugin that adds jobs to namespaces. As it uses setns() system call -
which can only work on the calling process - the plugin thus relies
on being called from the calling process.

Bug 6567.

Every once in a while I want to remove an element from a list but not
delete it.  This function does that.

Bug 6878

Brought the option in line with the "numtasks" option you use when
not specifying --step. Preserved backwards compatbility for "numtask"
for steps. Also upated docs and expect test.

Bug 6861

Bug 6657.

Bug 6256

Bug 6236

bug 6878

just to help insure no vestigial jobs last long

bug 6878

The "cmd" argument to the function was ignored (and was unusable as
a single token in any case). Just pass a sleep time instead.

bug 6878

bug 6878

Bug 6015.

Bug 6278.

Bug 6278.

Bug 6278.

Bug 6278.

Bug 6278.

Bug 6278.

Bug 6278.