From ef63aa50e2358a9e2e8eeefb6f6b9f969756f34e Mon Sep 17 00:00:00 2001 From: Juliana Fajardini Date: Tue, 17 Sep 2024 15:50:37 -0300 Subject: [PATCH] doc/configuration: improve emergency-recovery docs When removing mentions to `prune-flows` a few inconsistencies for how we write and refer to `emergency-recovery` were left behind, still. --- doc/userguide/configuration/suricata-yaml.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/userguide/configuration/suricata-yaml.rst b/doc/userguide/configuration/suricata-yaml.rst index ce7cd76a85..26c1e9e678 100644 --- a/doc/userguide/configuration/suricata-yaml.rst +++ b/doc/userguide/configuration/suricata-yaml.rst @@ -1071,7 +1071,7 @@ flow-engine goes into the emergency-mode. In this mode, the engine will make use of shorter time-outs. It lets flows expire in a more aggressive manner so there will be more space for new Flows. -Emergency_recovery defines the percentage of flows that the engine needs to +``emergency-recovery`` defines the percentage of flows that the engine needs to prune before clearing the **emergency mode**. The default ``emergency-recovery`` value is 30. This is the percentage of prealloc'd flows after which the flow -engine will be back to normal (when 30 percent of the 10000 flows are @@ -1084,7 +1084,7 @@ completed). :: - emergency_recovery: 30 #Percentage of 10000 prealloc'd flows. + emergency-recovery: 30 #Percentage of 10000 prealloc'd flows. Flow Time-Outs ~~~~~~~~~~~~~~