know how to connect back when in the federation.

to the common spot in the persist_conn code.

working with the slurmctld.

you will not be able to correctly handle multiple rpc messages.

(The previous code would send one sub-message back instead of a
DBD_GOT_MULT_MSG containing all the responses)

the slurmdbd_msg_t.

Also making calls more generic to handle things better when doing
this in the slurmctld later.

persist rc opportunities currently using DBD_RC.

the function.

the wire.

the wire.

persist_conn instead.

code.

functions.

structure itself.

to be able to simplify this structure to use a persist_conn later.

the receiving end use the same structure.

dbd_init messages.  Should work with 16.05 sacct/slurmctlds using the
old messages.

this in the future.  Should be easy to move to the end.  Wasn't sure
why it was looked at at the beginning.

of the local functions.  There will be more removal from the
slurmdbd_defs files in the future as the persist_conn logic grows.

msg_type first.  So we add this to the header to make it so.

will be going away in later commits (pack anyway) so that is why we
don't versionize the pack.

the twain shall meet.

for messages that have already been received.

slurmdbd communication code.

Restore ability to manually power down nodes, broken in 15.08.12
in commit b4904661

The patch introduced in commit b4904661 (not powering down dead node) has a bad side effect.  Adding the "(node_ptr->last_idle != 0)" condition prevents from powering down nodes with the following command:

scontrol update nodename=nX state=power_down

because the state update function relies on zeroing the "last_idle" variable when a power_down is requested (see src/slurmctld/node_mgr.c, line 1589).

Reverting this commit should solve the problem...but I let you decide...

Didier GAZEN

bug 3093

node_features/knl_cray: If a node is rebooted outside of Slurm's direction,
    update it's active features with current MCDRAM and NUMA mode information.
bug 3071

Will be appended to usernames if --mail-user is not explicitly set for the
job and email notifications are requested.

Bug 3089.