users/accounts/flags

correctly for current job.

realtime server.

start in the future but is able to run now.

accounting as well.

We've discovered that our implementation of proctrack/cgroups includes
internal threads as well as the process pids so that "scontrol list pids"
shows them as well. The attached patch (courtesy of Matthieu Hautreux)
to 2.4.2 fixes this problem.

running on it are preemptable by scheduling job.

reported some suspended time.

static blocks.

when none are requested.  The Block allocator sets it up temporarily so
this isn't needed.

and a job comes through backfill and can fit on the block without ending
jobs don't set an end_time for the running jobs since they don't need to
end to start the job.

Return ESLURM_NODES_BUSY rather than ESLURM_NODE_NOT_AVAIL error on job
submit when required nodes are up, but completing a job or in exclusive
job allocation.

previous 20 minute time limit.  The previous behavior would fail for
large files 20 minutes into the transfer.

Close the batch job's environment file when it contains no data to avoid
leaking file descriptors.

to operate the same way salloc or sbatch did and assign a task per cpu
by default instead of task per node.

correctly.  Before the errno wasn't being checked correctly

correctly as of IBM driver V1R1M1 efix 008.

configured correctly.

current or in the past.

from Mark Nelson

Using the syscalls directly rather than calling bin/(u)mount via
system() avoids a few fork + exec calls, and provides better error
handling if something goes wrong.

Users of this functionality are also updated to use slurm_strerror in
order to provide a more informative error message.

The mount and umount syscalls are Linux-specific, but so are cgroups
so no portability is lost.

Using the syscalls directly rather than calling bin/(u)mount via
system() avoids a few fork + exec calls, and provides better error
handling if something goes wrong.

Users of this functionality are also updated to use slurm_strerror in
order to provide a more informative error message.

The mount and umount syscalls are Linux-specific, but so are cgroups
so no portability is lost.

Using the syscalls directly rather than calling bin/(u)mount via
system() avoids a few fork + exec calls, and provides better error
handling if something goes wrong.

Users of this functionality are also updated to use slurm_strerror in
order to provide a more informative error message.

The mount and umount syscalls are Linux-specific, but so are cgroups
so no portability is lost.

    the current plugin has been loaded when using runjob_mux_refresh_config