honored correctly.  I also put in nice notes where the values aren't
to be altered.

* Specify MinNodes via "scontrol update partition".
* Whenever the zero-node allocation ends, the frontend node is left in a state of COMPLETING until scontrol reconfigure is issued (this doesn't appear to impact the performance of the front end node as other jobs can still be submitted including other zero-node jobs).

system of different size than actual hardware.

handled.

cpus in task/cgroup plugin

Cray - Add support for zero compute note resource allocation to run batch
script on front-end node with no ALPS reservation. Useful for pre- or post-
processing. NOTE: The partition must be configured with MinNodes=0.

batch jobs.

Before it could break before which could mess things up on a Q.

SELECT_NAV

respected block allocators.  This also catches the conn-types like
T,T,N,N on a Q system where before those didn't work correctly.

just return a bad result instead of talk to the database.

clause

Sinfo output format of "%P" now prints "*" after default partition even if
no field width is specified (previously included "*" only if no field width
was specified. Added output format of "%R" to print partition name only
without identifying the default partition with "*").

fatal when no from the controller.

Show this HTML in a new window?
There is a minor problem with the display of partition names in
"sinfo".  Without options, the partition name field displays a
asterisk "*" at the end of the name of the Default partition.  If you
specify a formatting option which contains the %P field specifier with
a width option (e.g., sinfo -o %8P) the asterisk also is appended to
the default partition name.  With no width option, the "%P" displays
the name based on the full length of the name string, however, no "*"
is appended on the default partition name.

The attached patch for version 2.4.0-pre4 corrects the problem so that
the "*" is correctly appended when %P with no width specifier is
used. The patch will also apply to version 2.3.4.

  -Don Albert-

If a node or partition name is duplicated in slurm.conf, then log
it using error() and ignore the duplicate record. Update documentation
to be more clear

starts.

SLURM wouldn't create another overlapping block on a job requesting that
size of block.