to a bluegene cluster.

already pinged it on startup the unresponding flag would be removed from
the frontend node.

mark front end node down.

state change while the realtime server is running.

running on.

mark front end node down.

Cray - For srun wrapper when creating a job allocation, set the default job
name to the executable file's name. Ignore leading directory names in the path.

Cray - Enable logging of BASIL communications with environment variables.
Set XML_LOG to enable logging. Set XML_LOG_LOC to specify path to log file
or "SLURM" to write to SlurmctldLogFile or unset for "slurm_basil_xml.log".
Based on work by Steve Tronfinoff, CSCS.

permit the srun and salloc commands to be executed in the background
on Cray systems

permit the srun and salloc commands to be executed in the background
on Cray systems

Add new job state reason of "FrontEndDown" which applies only to Cray and
IBM BlueGene systems.

the queue when trying to place a larger than midplane job.

an admin updates the node to idle/resume the compute nodes will go
instantly to idle instead of idle* which means no response.

gone.  Previously it had a timelimit which has proven to not be the right
thing.

In cray/srun wrapper, only include aprun "-q" option when srun "--quiet"
option is used.

Change default SchedulerParameters max_switch_wait field value from 60 to
300 seconds.

Patch from Aleksej Saushev.

CnodeCount/CnodeErrCount so to point out there are cnodes in an error state
on the block.  Draining the block and having it reboot when all jobs are
gone will clear up the cnodes in Software Failure.

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.

blocks.

are full allocation jobs, and others that are smaller.

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.

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.