From 5105a91c9dc3210e242dff156b861e77aa80959a Mon Sep 17 00:00:00 2001 From: Michael Mattioli Date: Sun, 14 Jul 2019 17:35:17 -0400 Subject: [PATCH] Correct documentation of final profiles The documentation for krb5.conf explaining final values is incorrect. Only sections and subsections may usefully be marked as final, and final designations only apply to later files, not to the same file. [ghudson@mit.edu: corrected and shortened documentation; rewrote commit message] ticket: 8821 (new) tags: pullup target_version: 1.17-next --- doc/admin/conf_files/krb5_conf.rst | 16 +++++----------- 1 file changed, 5 insertions(+), 11 deletions(-) diff --git a/doc/admin/conf_files/krb5_conf.rst b/doc/admin/conf_files/krb5_conf.rst index e4de1a0c1a..3856fc46ed 100644 --- a/doc/admin/conf_files/krb5_conf.rst +++ b/doc/admin/conf_files/krb5_conf.rst @@ -35,17 +35,11 @@ or:: baz = quux } -Placing a '\*' at the end of a line indicates that this is the *final* -value for the tag. This means that neither the remainder of this -configuration file nor any other configuration file will be checked -for any other values for this tag. - -For example, if you have the following lines:: - - foo = bar* - foo = baz - -then the second value of ``foo`` (``baz``) would never be read. +Placing a '\*' after the closing bracket of a section name indicates +that the section is *final*, meaning that if the same section appears +within a later file specified in **KRB5_CONFIG**, it will be ignored. +A subsection can be marked as final by placing a '\*' after either the +tag name or the closing brace. The krb5.conf file can include other files using either of the following directives at the beginning of a line:: -- 2.47.2