diff options
| author | Renaud Métrich <rmetrich@redhat.com> | 2020-08-20 13:00:37 +0200 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2020-09-01 17:20:23 +0200 |
| commit | 3e5f04bf6468fcb79c080f02b0eab08f258bff0c (patch) | |
| tree | 4bd8f30a63684745216e7cde2d56436026f531ac /man/systemd.socket.xml | |
| parent | f77d6ec9539fd87eb3ecad3a742ac684cc6dc5d2 (diff) | |
| download | systemd-3e5f04bf6468fcb79c080f02b0eab08f258bff0c.tar.gz | |
socket: New option 'FlushPending' (boolean) to flush socket before entering listening state
Disabled by default. When Enabled, before listening on the socket, flush the content.
Applies when Accept=no only.
Diffstat (limited to 'man/systemd.socket.xml')
| -rw-r--r-- | man/systemd.socket.xml | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/man/systemd.socket.xml b/man/systemd.socket.xml index 29ce0b1c20..1bcbef2033 100644 --- a/man/systemd.socket.xml +++ b/man/systemd.socket.xml @@ -428,6 +428,18 @@ </varlistentry> <varlistentry> + <term><varname>FlushPending=</varname></term> + <listitem><para>Takes a boolean argument. May only be used when + <option>Accept=no</option>. If yes, the socket's buffers are cleared after the + triggered service exited. This causes any pending data to be + flushed and any pending incoming connections to be rejected. If no, the + socket's buffers won't be cleared, permitting the service to handle any + pending connections after restart, which is the usually expected behaviour. + Defaults to <option>no</option>. + </para></listitem> + </varlistentry> + + <varlistentry> <term><varname>MaxConnections=</varname></term> <listitem><para>The maximum number of connections to simultaneously run services instances for, when |