keep-alive()

Type: yes or no

Default: yes

Description: Specifies whether connections to sources should be closed when syslog-ng is forced to reload its configuration (upon the receipt of a SIGHUP signal).
Note that this applies to the server (source) side of the syslog-ng connections, client-side (destination) connections are always reopened after receiving a HUP signal unless the keep-alive option is enabled for the destination.

From: syslog-ng <syslog-ng-bounces@lists.balabit.hu> on behalf of johns spam <jspam@skopis.com>
Sent: Thursday, January 16, 2020 13:01
To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu>
Subject: [syslog-ng] Go away

CAUTION: This email originated from outside of the organization. Do not follow guidance, click links, or open attachments unless you recognize the sender and know the content is safe.

Hello,

I am wondering if there is any facility to tell a client to go away? i.e.

https://http2.github.io/http2-spec/#GOAWAY

I know syslog-ng is not http2 but is there any side-channel mechanism a central server can use to make a client go away?

The use case I am thinking is doing a rolling restart of a pool of syslog-ng central server.

I think this could also be useful to cycle connections periodically, i.e. to rebalance connections to a central server.

Thanks