When the optional max_time is not specified for --switches=count, the site
max (SchedulerParameters=max_switch_wait=seconds) is used for the job.
Based on patch from Rod Schultz.

Fixes a bunch of warnings of this type
warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body

Patch from Aleksej Saushev.

Moe,

Here it is, I have added a subroutine to env.c to
unset the user's environment and then called it
from sbatch in main. I also removed the comment
from the sbatch man page indicating that it
wasn't working the same for a regular user as
it did for Moab. It should now be functionally
the same.

I think there is still a difference between how
sbatch functions with an environment in a file
than it does from when Moab excve'd the environment.
However, I'm not sure what it would be at this
point.

Again,  for so many iterations....

Phil

Moe,

After doing more extensive testing, I came to realize
that we had made a bad basic assumption. We believed
that the user's environment should only be what was
sent in the file via the --export-file option.

However, that broke the previous behavior, especially
in regard to Moab jobs. It also caused the SLURM
defined environment variables to be lost as well.

This patch will enable the correct behavior for Moab
on top of SLURM whne using the --export-file option,
but the behavior is less that pefect for using it
stand alone with sbatch. When using the option with
sbatch as a user, the file environment is read in,
and then when the env_array_merge is made, some
variables may get overwritten. This is good for
the SLURM and MPI vairables, but not so good for
others., The problem is trying to reconcile two
sources of environment is very problematic.

I also added a caveat in the man page.

I made changes in my branch of SchedMD SLURM
for 2.3, here is the patch.

Phil

We replaced references to "pipe" with a more generic "file descriptor".
We also replaced a while loop in env.c with a for loop.

This new sbatch option allows the user to specify a file containing
environment variables to be used in the jobs execution environment.

It used to be listed as "--switch=" rather than "--switches="

Fix bug in srun --multi-prog configuration file to avoid printing duplicate
record error when "*" is used at the end of the file for the task ID. It
means all task IDs not otherwise identified.

Patsh from Rod Schulz, Bull.

Note that if a job is requeued, it's submit time is changed and the record appears
as a duplicate job with a different submit time. Patch by Bill Brophy, Bull.

Backfill scheduling - Add SchedulerParameters configuration parameter of
"bf_res" to control the resolution in the backfill scheduler's data about
when jobs begin and end. Default value is 60 seconds (used to be 1 second).

This patch contains corrections for spelling errors in the code and
improvements for some man pages. Patch from Gennaro Oliva.

Update cgroup.conf(5) with documentation for new parameters
CgroupMountpoint, MinRAMSpace, MaxRAMPercent and MaxSwapPercent.
Also include information about handling of AllowedRAMSpace when
memory is not explicitly allocated by SLURM.

Advise use of the logrotate tool in order to avoid SLURM log files
from growing too large. Patch from Rod Shultz, Bull.

Do not treat the absence of a gres.conf file as a fatal error on systems
configured with GRES, but set GRES counts to zero. These counts can be
Counts can be altered by node_config_load() in the gres plugin.

The "+" sign only appears to indicate that there is more information than the current field width can hold.  For example  "CANCELLED+"  can indicate that the state is actually "CANCELLED by nnn".   Increasing the field width with the %NUMBER format modifier will show this. Patch by Don Albert, Bull.

Add cray.conf parameter of SyncTimeout, maximum time to defer job
scheduling if SLURM node or job state are out of synchronization with ALPS.

partition in the slurm.conf.

Change "AveVSize" to "AveVMSize" in sstat man page to match the code.
Addresses SchedMD bugzilla entry 7 by Cray.

Modify salloc, sbatch, and srun node specification parsing to accept
a number followed by a suffix of "M" to multiply the numeric value
by 1,048,576 (1024 x 1024).

Large-scale update of bluegene.conf man page to incorporate BlueGene/Q
information plus some general updates.

on a Bluegene/Q system when srun's --test-only option is used within
an existing allocation then launch the job directly with the slurmd
daemon and do not use IBM's "runjob" command. Useful for testing.