[SSSD] [PATCH] MAN: Clarify debug_level a bit
Jakub Hrozek
jhrozek at redhat.com
Tue Mar 17 12:27:34 UTC 2015
On Tue, Mar 17, 2015 at 01:09:49PM +0100, Lukas Slebodnik wrote:
> On (17/03/15 13:03), Jakub Hrozek wrote:
> >Hi,
> >
> >see the attached man page patch.
>
> >From 51a1175eaa278365eba4e78cbeeedb62001498f9 Mon Sep 17 00:00:00 2001
> >From: Jakub Hrozek <jhrozek at redhat.com>
> >Date: Tue, 17 Mar 2015 13:02:09 +0100
> >Subject: [PATCH] MAN: Clarify debug_level a bit
> >
> >Some users are confused about placement of the debug_level directive or
> >the location of the log files. Clarify both in the man page.
> >---
> > src/man/include/debug_levels.xml | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> >diff --git a/src/man/include/debug_levels.xml b/src/man/include/debug_levels.xml
> >index 631e19d3905be6ecaf4f00d91038de2b4c981f84..8bfc67b1534640227aaa3e92b7df54968470ddb8 100644
> >--- a/src/man/include/debug_levels.xml
> >+++ b/src/man/include/debug_levels.xml
> >@@ -7,6 +7,14 @@
> > disable specific levels (such as if you wish to suppress a level).
> > </para>
> > <para>
> >+ Please note that each SSSD service logs into its own log
> >+ file. Also please note that enabling <quote>debug_level</quote>
> >+ in the <quote>[sssd]</quote> section only enables debugging just
> >+ for the sssd process itself, not for the responder or provider
> >+ processes. The <quote>debug_level</quote> parameter should be
> >+ added to all sections that you wish to produce debug logs from.
> >+ </para>
>
> Do we want to also raise awareness of sss_debuglevel (8)
> Pleaple don't know about it.
>
> It is just mentioned in see also section.
>
> SEE ALSO
> sssd(8), sssd.conf(5), sssd-ldap(5), sssd-krb5(5), sssd-simple(5),
> sssd-ipa(5), sssd-ad(5), sssd-sudo(5),sss_cache(8), sss_debuglevel(8),
> sss_groupadd(8), sss_groupdel(8), sss_groupshow(8), sss_groupmod(8),
> sss_useradd(8), sss_userdel(8), sss_usermod(8), sss_obfuscate(8),
> sss_seed(8), sssd_krb5_locator_plugin(8), sss_ssh_authorizedkeys(8),
> sss_ssh_knownhostsproxy(8),sssd-ifp(5),pam_sss(8). sss_rpcidmapd(5)
>
> LS
Good idea, see attached patch.
-------------- next part --------------
>From bfe31382b95bd1a61a5186e57553375b83c2c358 Mon Sep 17 00:00:00 2001
From: Jakub Hrozek <jhrozek at redhat.com>
Date: Tue, 17 Mar 2015 13:02:09 +0100
Subject: [PATCH] MAN: Clarify debug_level a bit
Some users are confused about placement of the debug_level directive or
the location of the log files. Clarify both in the man page.
Also add a pointer to sss_debuglevel.
---
src/man/include/debug_levels.xml | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/src/man/include/debug_levels.xml b/src/man/include/debug_levels.xml
index 631e19d3905be6ecaf4f00d91038de2b4c981f84..0711cb5600b90b1c7dfc4a7728beff5b245f866a 100644
--- a/src/man/include/debug_levels.xml
+++ b/src/man/include/debug_levels.xml
@@ -7,6 +7,25 @@
disable specific levels (such as if you wish to suppress a level).
</para>
<para>
+ Please note that each SSSD service logs into its own log
+ file. Also please note that enabling <quote>debug_level</quote>
+ in the <quote>[sssd]</quote> section only enables debugging just
+ for the sssd process itself, not for the responder or provider
+ processes. The <quote>debug_level</quote> parameter should be
+ added to all sections that you wish to produce debug logs from.
+ </para>
+ <para>
+ In addition to changing the log level in the config file using
+ the <quote>debug_level</quote> parameter, which is persistent, but
+ requires SSSD restart, it is also possible to change the debug level
+ on the fly using the
+ <citerefentry>
+ <refentrytitle>sss_debuglevel</refentrytitle>
+ <manvolnum>8</manvolnum>
+ </citerefentry>
+ tool.
+ </para>
+ <para>
Currently supported debug levels:
</para>
<para>
--
2.1.0
More information about the sssd-devel
mailing list