Gerrit Renker:  I found an easier test: after making sure that stdin is not
 redirected, check whether there is a non-negative terminal process group (it
 is -1 if there is no controlling terminal).

 Also, I think that the heuristic "only interactive if from login shell" is
 needlessly complicated/obscure. Most (if not all) shells that support job
 control place processes in their own process group (pid == pgrp): it now uses
 this as indicator of interactive mode.

The following tests now pass:

  salloc &			# from login shell and from nested shell
  salloc --no-shell&		# ok
  salloc /bin/date&		# wants to be placed into the foreground
  salloc /bin/date </dev/null &	# ok

  setsid salloc	 		# complains there is no controlling terminal
  setsid salloc --no-shell&	# ok

    or resumed when appropriate.

    ("setsid salloc ..." is disabled). Patch from Gerrit Renker, CSCS.

    foreground. Patch from Gerrit Renker, CSCS.
    a) salloc is not run in allocation-only (--no-shell) mode,
    b) stdin is from a terminal (tcgetattr does not return ENOTTY),
    c) salloc has been invoked from a login shell (not a nested one),
    d) salloc has been configured at compile-time to support background
       execution and is not currently in the background process group.

Fix for handling job names with a "'" in the name within MySQL accounting. Patch from Gerrit Renker, CSCS.

    associated with a given NodeHostName when running multiple slurmd daemons
    per compute node (typically used for testing purposes). Patch from
    Matthieu Hautreux, CEA.

    MessageTimeout configuration parameter rather than always 3 seconds.
    Patch from Matthieu Hautreux, CEA.

    Bjorn-Helge Mevik, University of Oslo.

   block second distribution and cpus-per-task > 1" bug.

    option. Patches from Rod Schulz, Bull.

-- Removed remnant code for enforcing max sockets/cores/threads in the
   cons_res plugin.  This was responsible for a bug reported by Rod Schultz.

    set, then salloc can execute in the background. Otherwise a message will be
    printed and the job allocation halted until brought into the foreground.

    terminal's state.

Fix issue when updating database for clusters that were previously deleted before upgrade to 2.2 database.

    IDLE (in case the previous node state was DOWN).

    job is in a pending state, then send the request directly to the slurmctld
    daemon and do not attempt to send the request to slurmd daemons, which are
    not running the job anyway.

    consider the job's time limit when attempting to backfill schedule. The job
    will just be preempted as needed at any time.

    Priority.

    expected start time was too far in the future for the backfill scheduler
    to compute.

    values as "*" rather than 65534. Patch from Rod Schulz, BULL.

    the job's priority using scontrol's "update jobid=..." rather than its 
    "hold" or "holdu" commands.

Fixed issue when using a storage_accounting plugin directly without the slurmDBD updates weren't always sent correctly to the slurmctld, appears to OS dependent, reported by Fredrik Tegenfeldt.

    it were removed from the job's allocation. Now only the tasks on those
    nodes are terminated.