From ab8a316d07a3d385cf3ddfdaa1c75c149e3c565d Mon Sep 17 00:00:00 2001 From: Hofi Date: Wed, 26 Aug 2026 11:52:24 +0200 Subject: [PATCH] keep-alive: rephrased the keep-alive behavior according to the current implementation Signed-off-by: Hofi --- _includes/doc/admin-guide/options/keep-alive.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/_includes/doc/admin-guide/options/keep-alive.md b/_includes/doc/admin-guide/options/keep-alive.md index 4cd8a8fb..a0c07ed2 100644 --- a/_includes/doc/admin-guide/options/keep-alive.md +++ b/_includes/doc/admin-guide/options/keep-alive.md @@ -3,9 +3,8 @@ | Accepted values: | `yes`, `no` | | Default: | `yes` | -*Description:* Specifies whether connections to sources should be closed -when {{ site.product.short_name }} is forced to reload its configuration (upon the receipt -of a SIGHUP signal). Note that this applies to the server (source) side -of the {{ site.product.short_name }} connections, client-side (destination) connections are -always reopened after receiving a HUP signal unless the keep-alive -option is enabled for the destination. +*Description:* Specifies whether connections should be kept open across +configuration reloads (upon the receipt of a SIGHUP signal). When set to +`yes` (the default), {{ site.product.short_name }} preserves existing +connections when reloading its configuration. Set it to `no` to force +{{ site.product.short_name }} to close and reopen connections on every reload.