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 edffc7c2616c49ffc003236f1785348494651721..eeca5b44fce7b45f0ed78383d05e5a0b8c36c0b4 100644 (file)
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -7409,10 +7409,13 @@ default-server [name <name>] [from <origin>] [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