for a long time after the SLURM job has been flushed from the system
we don't have to worry about rebooting the block to sync the system.

process when job is killed by scancel.

expired.

software error before.

updates.

state when already in error state.

sub-allocation steps of sub-block jobs.

blocks.

than your allocation.

are full allocation jobs, and others that are smaller.

Conflicts:
	src/slurmctld/node_scheduler.c

c0a7a7a4

fixed the problem

while jobs are running on them.

is a convenience function in BSD and glibc that internally calls
the equivalent of

    int masterfd = open("/dev/ptmx", flags);
    grantpt (masterfd);
    unlockpt (masterfd);
    int slavefd = open (slave, O_RDRW|O_NOCTTY);

(in psuedocode)

On Linux, with some combinations of glibc/kernel (in this
case glibc-2.14/Linux-3.1), the equivalent of grantpt(3) was failing
in slurmstepd with EPERM, because the allocated pty was getting
root ownership instead of the user running the slurm job.

From the POSIX description of grantpt:

 "The grantpt() function shall change the mode and ownership of the
  slave pseudo-terminal device... The user ID of the slave shall
  be set to the real UID of the calling process..."

 http://pubs.opengroup.org/onlinepubs/007904875/functions/grantpt.html

This means that for POSIX-compliance, the real user id of slurmstepd
must be the user executing the SLURM job at the time openpty(3) is
called. Unfortunately, the real user id of slurmstepd at this
point is still root, and only the effective uid is set to the user.

This patch is a work-around that uses the (non-portable) setresuid(2)
system call to reset the real and effective uids of the slurmstepd
process to the job user, but keep the saved uid of root. Then after
the openpty(3) call, the previous credentials are reestablished
using the same call.

of it's dimensions of length 3.  There is a limitation in the IBM I/O
subsystem that is problematic with multiple sub-blocks with a dimension
of length 3, so we will disallow them to be able to be created.  This
mean you if you ask the system for an allocation of 12 c-nodes you will
be given 16.  If this is ever fix in BGQ you can remove this patch.

Validate MPI rank values returned in test of MPI

Fix for srun allocating running within existing allocation with --exclude
option and --nnodes count small enough to remove more nodes.

    > salloc -N 8
    salloc: Granted job allocation 1000008
    > srun -N 2 -n 2 --exclude=tux3 hostname
    srun: error: Unable to create job step: Requested node configuration is not available

Patch from Phil Eckert, LLNL.

Add call to mpi_hook_slurmstepd_prefork() from slurmstep
immediately prior to fork/exec of user tasks.
Patch from Hongjia Cao, NUDT.

Add a generic data forwarding protocol to slurmd which uses its
existing hierarchical communications protocol.
Patch from Hongjia Cao, NUDT.

Patch from Hongjia Cao, NUDT.

Patch from Hongjia Cao, NUDT.

Make step launch API more robust if there are NULL pointers.
Patch from Hongjia Cao, NUDT.