Blame SOURCES/0064-SYSTEMD-Re-read-KCM-configuration-on-systemctl-resta.patch

71e593
From c53fc08a70679b181b0eff6422f199a51d527e67 Mon Sep 17 00:00:00 2001
71e593
From: Jakub Hrozek <jhrozek@redhat.com>
71e593
Date: Tue, 9 Oct 2018 15:41:44 +0200
71e593
Subject: [PATCH 64/66] SYSTEMD: Re-read KCM configuration on systemctl restart
71e593
 kcm
71e593
MIME-Version: 1.0
71e593
Content-Type: text/plain; charset=UTF-8
71e593
Content-Transfer-Encoding: 8bit
71e593
71e593
Related:
71e593
https://pagure.io/SSSD/sssd/issue/3862
71e593
71e593
Uses the sssd command together with the --genconf-section=kcm option to
71e593
refresh the kcm configuration when the sssd-kcm systemd service is
71e593
restarted.
71e593
71e593
This allows the administrator to e.g. just drop a snippet to
71e593
/etc/sssd.conf.d/ or create the [kcm] section directly in the main sssd
71e593
config file, then just restart the sssd-kcm service for the changes to
71e593
apply.
71e593
71e593
Reviewed-by: Michal Židek <mzidek@redhat.com>
71e593
---
71e593
 src/man/sssd-kcm.8.xml               | 33 ++++++++++++++++++++++++++++
71e593
 src/sysv/systemd/sssd-kcm.service.in |  1 +
71e593
 2 files changed, 34 insertions(+)
71e593
71e593
diff --git a/src/man/sssd-kcm.8.xml b/src/man/sssd-kcm.8.xml
71e593
index ec27aa57b..fff8b0a16 100644
71e593
--- a/src/man/sssd-kcm.8.xml
71e593
+++ b/src/man/sssd-kcm.8.xml
71e593
@@ -127,6 +127,39 @@ systemctl enable sssd-kcm.socket
71e593
         </para>
71e593
     </refsect1>
71e593
 
71e593
+    <refsect1 id='debugging'>
71e593
+        <title>OBTAINING DEBUG LOGS</title>
71e593
+        <para>
71e593
+            The sssd-kcm service is typically socket-activated
71e593
+            <citerefentry>
71e593
+                <refentrytitle>systemd</refentrytitle>
71e593
+                <manvolnum>1</manvolnum>
71e593
+            </citerefentry>. To generate debug logs, add the following
71e593
+            either to the <filename>/etc/sssd/sssd.conf</filename>
71e593
+            file directly or as a configuration snippet to
71e593
+            <filename>/etc/sssd/conf.d/</filename> directory:
71e593
+            <programlisting>
71e593
+[kcm]
71e593
+debug_level = 10
71e593
+            </programlisting>
71e593
+            Then, restart the sssd-kcm service:
71e593
+            <programlisting>
71e593
+systemctl restart sssd-kcm.service
71e593
+            </programlisting>
71e593
+            Finally, run whatever use-case doesn't work for you. The KCM
71e593
+            logs will be generated at
71e593
+            <filename>/var/log/sssd/sssd_kcm.log</filename>. It is
71e593
+            recommended to disable the debug logs when you no longer need
71e593
+            the debugging to be enabled as the sssd-kcm service can generate
71e593
+            quite a large amount of debugging information.
71e593
+        </para>
71e593
+        <para>
71e593
+            Please note that configuration snippets are, at the moment,
71e593
+            only processed if the main configuration file at
71e593
+            <filename>/etc/sssd/sssd.conf</filename> exists at all.
71e593
+        </para>
71e593
+    </refsect1>
71e593
+
71e593
     <refsect1 id='options'>
71e593
         <title>CONFIGURATION OPTIONS</title>
71e593
         <para>
71e593
diff --git a/src/sysv/systemd/sssd-kcm.service.in b/src/sysv/systemd/sssd-kcm.service.in
71e593
index 8d689bfd7..5c82bee7d 100644
71e593
--- a/src/sysv/systemd/sssd-kcm.service.in
71e593
+++ b/src/sysv/systemd/sssd-kcm.service.in
71e593
@@ -9,4 +9,5 @@ Also=sssd-kcm.socket
71e593
 
71e593
 [Service]
71e593
 Environment=DEBUG_LOGGER=--logger=files
71e593
+ExecStartPre=-@sbindir@/sssd --genconf-section=kcm
71e593
 ExecStart=@libexecdir@/sssd/sssd_kcm --uid 0 --gid 0 ${DEBUG_LOGGER}
71e593
-- 
71e593
2.19.1
71e593