diff options
| author | Lukas Slebodnik <lslebodn@redhat.com> | 2016-07-01 08:56:43 +0200 |
|---|---|---|
| committer | Lukas Slebodnik <lslebodn@redhat.com> | 2016-07-05 20:45:36 +0200 |
| commit | b6cd138f1e444d73295d3d3869de2dc4194f1742 (patch) | |
| tree | 627cb36ede52c7c1201bfbc1a6d13a9b3bba4f37 | |
| parent | c744f9df3b6b169c8c70fcfd063ab6402229218e (diff) | |
| download | sssd-b6cd138f1e444d73295d3d3869de2dc4194f1742.tar.gz sssd-b6cd138f1e444d73295d3d3869de2dc4194f1742.tar.xz sssd-b6cd138f1e444d73295d3d3869de2dc4194f1742.zip | |
MAN: Remove leading spaces from elements programlisting
Docbook documentatin for the programlisting elemnt says:
Description:
A ProgramListing is a verbatim environment for program source
or source fragment listings. ProgramListings are often placed
in Examples or Figures so that they can be cross-referenced
from the text.
Processing Expectations:
Formatted as a displayed block. This element is displayed
"verbatim"; whitespace and linebreaks within this element
are significant. ProgramListings are usually displayed
in a fixed width font.
Reviewed-by: Jakub Hrozek <jhrozek@redhat.com>
| -rw-r--r-- | src/man/idmap_sss.8.xml | 11 | ||||
| -rw-r--r-- | src/man/pam_sss.8.xml | 2 |
2 files changed, 6 insertions, 7 deletions
diff --git a/src/man/idmap_sss.8.xml b/src/man/idmap_sss.8.xml index 5ba4e212e..4c26a17f9 100644 --- a/src/man/idmap_sss.8.xml +++ b/src/man/idmap_sss.8.xml @@ -47,13 +47,12 @@ </para> <programlisting format="linespecific"> - [global] - security = domain - workgroup = MAIN - - idmap config * : backend = sss - idmap config * : range = 200000-2147483647 +[global] +security = domain +workgroup = MAIN +idmap config * : backend = sss +idmap config * : range = 200000-2147483647 </programlisting> </refsect1> diff --git a/src/man/pam_sss.8.xml b/src/man/pam_sss.8.xml index b03ac2dc8..dd395a06a 100644 --- a/src/man/pam_sss.8.xml +++ b/src/man/pam_sss.8.xml @@ -176,7 +176,7 @@ Smartcard is inserted the login manager will call a PAM stack which includes a line like <programlisting> - auth sufficient pam_sss.so allow_missing_name +auth sufficient pam_sss.so allow_missing_name </programlisting> In this case SSSD will try to determine the user name based on the content of the Smartcard, returns it to |