DOC: configuration: confuse "strict-mode" with "zero-warning"

4b10302fd8 ("MINOR: cfgparse: implement a simple if/elif/else/endif
macro block handler") introduces a confusion between "strict-mode" and
"zero-warning".

This patch fixes the issue by changing "strict-mode" by "zero-warning"
in section 2.4. Conditional blocks.

Must be backported as far as 2.4.
This commit is contained in:
William Lallemand 2025-08-28 17:31:27 +02:00
parent 21f7974e05
commit e0ec01849f

View File

@ -1272,8 +1272,8 @@ Four other directives are provided to report some status:
- .warning "message" : emit this message at level WARNING - .warning "message" : emit this message at level WARNING
- .alert "message" : emit this message at level ALERT - .alert "message" : emit this message at level ALERT
Messages emitted at level WARNING may cause the process to fail to start if the Messages emitted at level WARNING may cause the process to fail to start if
"strict-mode" is enabled. Messages emitted at level ALERT will always cause a "zero-warning" is enabled. Messages emitted at level ALERT will always cause a
fatal error. These can be used to detect some inappropriate conditions and fatal error. These can be used to detect some inappropriate conditions and
provide advice to the user. provide advice to the user.