Make srun logic work more like sbatch/salloc.

Jenkins was reporting unused function otherwise

Fix for when a feature is available, but not active on any node.

Enforce a job's timelimit based upon when it actually beings
  execution, after node reboot completes.
However the job will be changed for resource allocation from the
  start of allocation, include boot time.

# Conflicts:
#	src/slurmctld/node_mgr.c

Move logic that re-calculates a job's end time based upon delayed launch
into a separate function.

Please submit patches through our bugzilla instance.

(This would also show up on the issues page if we hadn't disabled it.)

a parsing option.

Dynamically set columns widths based on largest number in column.

Previous logic was failing if feature name not found

Add PID to both the slumctld code and cray capmc_suspend/resume programs

Previous logic would cause slurmctld shutdown to wait for completion
  of all power save (suspend and resume) programs according to their
  time limits, which could be huge. The new logic waits up to 10 second
  then orphans the processes.

The parsing of the configuration parameter failed with a prefix
  of "node_features" due to vestigial logic for a plugin type
  of "knl".

Was trying to set NUMA mode as MCNUMA and vise-versa
Also change capmc to specify mode before nids, which seems more robust.

the "fputs" function was aborting, trying to write a NULL string pointer.
Also found the log message was printing the configured and read names
  in the wrong order.

abort() rather than continue if pthread_mutex_ calls fail. better
to die early rather than continue on and risk corruption. mirrors
the (now removed) macro definitions from cbuf/hostlist/list.

accounting.

AccountUtilizationByUser report a parent could potentially (correctly)
be larger than the sum of it's children because of the way
accounting for reservations work.

was given with just an =, i.e. users= without specifying any users after
the =.

period.  This would only hit you if you rerolled a 15.08 prior to this
commit.

Don't expand on the format or arguments, these have changed in
16.05 already and may vary further with BB/generic support.

If job submit time is right at a second boundary, the test could fail

TEST: 15.37
spawn /home/jette/SLURM/install_smd/bin/salloc --begin now+60 --deadline now+600 --time-min 10 sleep 1^M
salloc: error: Job submit/allocate failed: Requested time limit is invalid (missing or exceeds some limit)^M

FAILURE: batch not submitted with a deadline too short
test15.37 FAILURE

[2016-02-12T15:53:53.005] _valid_job_part: job's min_time greater than deadline (10 > 2016-02-12T16:03:52)
[2016-02-12T15:53:53.005] _slurm_rpc_allocate_resources: Requested time limit is invalid (missing or exceeds some limit)

These are very unlikely to ever occur, but this helps harden the code.