From 3f5c45753a172bd1c713b318cd530c667a7f41b1 Mon Sep 17 00:00:00 2001 From: Eric Garver Date: Wed, 23 Dec 2020 09:22:30 -0500 Subject: [PATCH 09/22] docs(firewall-cmd): reload does not affect direct rules if FlushAllOnReload=no (cherry picked from commit b682ba874ef879797d681fb018ce3c7b9c57efdb) (cherry picked from commit ab4ce6fb13607dba4f8a0e771455ad34d3adb77a) --- doc/xml/firewall-cmd.xml.in | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/xml/firewall-cmd.xml.in b/doc/xml/firewall-cmd.xml.in index 3369c2d3f942..691117f3dbff 100644 --- a/doc/xml/firewall-cmd.xml.in +++ b/doc/xml/firewall-cmd.xml.in @@ -133,9 +133,9 @@ if they have not been also in permanent configuration. - Note: Runtime changes applied via the direct interface are not + Note: If FlushAllOnReload=no, runtime changes applied via the direct interface are not affected and will therefore stay in place until firewalld daemon - is restarted completely. + is restarted completely. For FlushAllOnReload, see firewalld.conf5. @@ -147,9 +147,9 @@ Reload firewall completely, even netfilter kernel modules. This will most likely terminate active connections, because state information is lost. This option should only be used in case of severe firewall problems. For example if there are state information problems that no connection can be established with correct firewall rules. - Note: Runtime changes applied via the direct interface are not + Note: If FlushAllOnReload=no, runtime changes applied via the direct interface are not affected and will therefore stay in place until firewalld daemon - is restarted completely. + is restarted completely. For FlushAllOnReload, see firewalld.conf5. -- 2.27.0