response to job completion RPC.

communication itself) fails 

If the allocation has been granted, it will release the job
allocation on the first SIGINT, and ignore any following SIGINT signals
while waiting for the user's command to exit.

If the allocation if pending, salloc revokes the allocation and exits.

Should all other signals have the same behaviour?

Required scontrol to use helper library.

statically linked.

as libslurm.  However, libslurmhelper exports ALL symbols, not just the
ones in the SLURM API.  This can be used by slurm commands that want to 
use both libcommon and libslurm functions. 

salloc: Granted job allocation 65539
salloc: Relinquishing job allocation 65539

g_slurm_auth_get_uid(). The original code was resulting in the
slaunch command having two different symbols g_context for the 
module slurm_auth.c. Some functions would use one symbol and 
other functions would use the other symbol resulting in extreme 
badness (zero pointers and seg faults).

morrone:/tmp$ echo | sbatch
sbatch: error: Batch script contains only whitespace!
morrone:/tmp$ echo -n | sbatch
sbatch: error: Batch script is empty!
morrone:/tmp$ echo foobar |sbatch
sbatch: error: This does not look like a batch script.  The first
sbatch: error: line must start with #! followed by the path to an interpreter.
sbatch: error: For instance: #!/bin/sh

ESLURM_TASKDIST_REQUIRES_OVERCOMMIT.

Fix but in new env.c code.

variables.
It can also support a VERY limitted overcommit.  It only works if you
are using all nodes in the allocation.  Need to make this work for a subset.