From: Amaury Denoyelle Date: Wed, 5 Aug 2026 09:24:58 +0000 (+0200) Subject: DOC: better explain that default-server are now preserved X-Git-Tag: v3.5-dev4~6 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=ac8b99ca460b6f491da0c57e3ac127f097341037;p=thirdparty%2Fhaproxy.git DOC: better explain that default-server are now preserved Complete default-server documentation by mentionning that default-server unnamed and named are now preserved after configuration parsing. This is already mentionned in the related keyword "tune.defaults.purge". However, as this is a major change, it is necessary to remind it directly in default-server section. No need to backport. --- diff --git a/doc/configuration.txt b/doc/configuration.txt index edffc7c26..eeca5b44f 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -7409,10 +7409,13 @@ default-server [name ] [from ] [param*] completing the previous one. This set of options can be reset by using the "from none" keyword value. - An unnamed default-server with no parameter set will automatically be purged - after parsing. As such, a final "default-server from none" statement will be - sufficient to release this unused memory, regardless of the global setting - "tune.defaults.purge" value. + By default, all default-server named and unnamed are preserved after + configuration parsing. This allows to reuse them for dynamic servers + creation. This behavior can be changed globally via "tune.defaults.purge" + keyword. An unnamed default-server with no parameter set will automatically + be purged after parsing. As such, a final "default-server from none" + statement will be sufficient to release this unused memory, regardless of the + global setting. See also: "server", section 5 about server options and global "tune.defaults.purge" option