Rename yes_or_no to boolean
The name yes_or_no was used only in two places and rest of the ARM
(except for the grammar glossary...) uses term boolean. Let's stick to
it.
(cherry picked from commit 0138e5c1d5)
This commit is contained in:
@@ -256,7 +256,7 @@ The command formats and their meanings are as follows:
|
||||
in ``krb5.conf``. If no realm is specified, the saved realm is
|
||||
cleared.
|
||||
|
||||
``check-names [yes_or_no]``
|
||||
``check-names [boolean]``
|
||||
This command turns on or off check-names processing on records to be added.
|
||||
Check-names has no effect on prerequisites or records to be deleted.
|
||||
By default check-names processing is on. If check-names processing
|
||||
|
||||
@@ -345,7 +345,7 @@ file documentation:
|
||||
``percentage``
|
||||
An integer value followed by ``%`` to represent percent.
|
||||
|
||||
``yes_or_no``
|
||||
``boolean``
|
||||
Either ``yes`` or ``no``. The words ``true`` and ``false`` are also accepted, as are the numbers ``1`` and ``0``.
|
||||
|
||||
.. _configuration_file_grammar:
|
||||
@@ -6076,7 +6076,7 @@ The :any:`trusted-keys` statement has been deprecated in favor of
|
||||
view view_name [ class ] {
|
||||
match-clients { address_match_list } ;
|
||||
match-destinations { address_match_list } ;
|
||||
match-recursive-only yes_or_no ;
|
||||
match-recursive-only <boolean> ;
|
||||
[ view_option ; ... ]
|
||||
[ zone_statement ; ... ]
|
||||
} ;
|
||||
|
||||
@@ -284,7 +284,7 @@ When using GSS\-TSIG, this command specifies the use of \fBrealm_name\fP rather
|
||||
in \fBkrb5.conf\fP\&. If no realm is specified, the saved realm is
|
||||
cleared.
|
||||
.TP
|
||||
.B \fBcheck\-names [yes_or_no]\fP
|
||||
.B \fBcheck\-names [boolean]\fP
|
||||
This command turns on or off check\-names processing on records to be added.
|
||||
Check\-names has no effect on prerequisites or records to be deleted.
|
||||
By default check\-names processing is on. If check\-names processing
|
||||
|
||||
Reference in New Issue
Block a user