Until now I've been using a single imsg to handle each messages and the imsg framework has a limit of around 16K for message. For almost all requests, this is fine. Except for Twrite and Tread. This is an attempt to make Twrite handle bigger buffers. The listener process just looks at how big a request is and split it up in multiple messages and the client process tries to remember the fid, position and missing data to continue the write. This means that a single Twrite can be split up in multiple write(2)s.

meant to be used from kamictl to dump all the opened fid by every connection.

this saves us from the small chance that a client accepted before reconf uses the flags from a listener post reconf.

drop connections in the handshake phase: the listener from where they've been accepted is now being replaced and its id is no more meaningful. Clients for which we have already sent an auth request are kept.

it's not so useful here and not (directly) used anywhere else.

and don't forget to free the current config!