Bug 14535

Bug 14535

Can also modify 'extra' in database with 'sacctmgr modify job'.

Bug 14535

xfree() already guards against free after free and free(NULL).

Bug 14535

Previous 8 commits.

Bug 14535

Bug 14535

Bug 14535

Bug 14535

Bug 14535

Bug 14535

Bug 14535

Expands on work done for bug 3745. Makes "extra" fully usable as a
submission option (--extra).

Moves extra from job_details struct to job_record_t.

Bug 14535

Bug 14535

If the on_data() callback fails but doesn't clear the input buffer, then
on_data() will be called in an infinite loop as there is still pending
data. This patch clears the input buffer on on_data() failing.

Remove explicit tty check for --pty=num as set_winsize() will provide
the same check later in _setup_one_job_env()

Ensure set_winsize() is always called in _setup_one_job_env() to avoid
--pty=num not having the terminal size info.

Allow for calling set_winsize() with other file descriptors.

Continuation of d319d7a9.

Bug 15560, 11081

Only remaining detail from load_config_response_msg().

The 21.08 protocol changed to only sending the list.

This is the master-specific version of 51f33fb9.

Bug 15555.

Burst buffer scripts that run in slurmscriptd use the burst_buffer and
select plugins. Initialize these plugins at startup instead of lazily
initializing these plugins.

Conitinuation of commits 7c1623dd and 22e052ba.

Bug 15244

Throw away 51f33fb9 intentionally, it'll be handled differently for 23.02.

Need to load the List representation of the configs for 21.08.
Otherwise this won't send updated configs to the 21.08 slurmds.

Regression from 82db921c.

Bug 15555.

Continuation of 3c2ebacd

Bug 15481

This is useless code after the old commit 8907004c since we no longer
use libjob_handle variable.

Bug 15401

Continuation of 13eb1050

One thing to note is the removal of

/* On a front end system always notify_srun instead of slurmd */

Which wasn't ever happening with launch/slurm because notify_srun_static
was never 1.

This code comes from edda3733 which appears to be directly related to
Bluegene.

This was primarily done when working with IBM's POE.
This kind of interaction is not in the foreseeable future.

This was needed for BlueGene and this functionality will most likely not
be needed in the future.