Previously the SIGCONT would be generated easily as part of gang
scheduling and cause the job step initiaition to abort.
This is being back-ported from SLURM v2.5/master.

Previously the SIGCONT would be generated easily as part of gang
scheduling and cause the job step initiaition to abort.

SIGTSTP causes IBM MPI to hand periodically

One of our testers discovered an inconsistency between trigger names that
are displayed with 'strigger --get' and the trigger names passed to trigger
programs.

One of our testers discovered an inconsistency between trigger names that
are displayed with 'strigger --get' and the trigger names passed to trigger
programs.

Conflicts:
	src/plugins/accounting_storage/mysql/as_mysql_job.c

Not sure how this could have worked with AIX/POE in the past as
POE was spawning two copies of the script

accounting as well.

set errno == ESLURM_INVALID_TIME_VALUE on error instead.