review feedback

SUSE · Jul 17, 2024 · 2e333a1 · 2e333a1
1 parent 6091172
commit 2e333a1
Show file tree

Hide file tree

Showing 4 changed files with 12 additions and 103 deletions.
diff --git a/concepts/systemd-manage-best-practices.xml b/concepts/systemd-manage-best-practices.xml
@@ -15,12 +15,12 @@
        xmlns:xlink="http://www.w3.org/1999/xlink"
        xmlns:trans="http://docbook.org/ns/transclusion">
        <info>
-        <title>Manage &systemd; best practices</title>
+        <title>Best practices for &systemd; management</title>
         <!--add author's email address-->
         <meta name="maintainer" content=" [email protected] " its:translate="no"/>
         <abstract>
             <para>
-            To manage &systemd;service, try some of the best practices that are equipped to handle different situations:
+            To manage &systemd;service, try certain best practices that are equipped to handle different situations:
             </para>
             </abstract>
         </info>

diff --git a/references/systemd-termination-signal-new.xml b/references/systemd-termination-signal-new.xml
@@ -21,37 +21,16 @@
       You can send a signal to a &systemd; service or to the individual processes that belong to a service.
     </para>
 
-    <important>
-      <para>The D-Bus service is the message bus for communication between &systemd; clients and the &systemd; manager that is running as PID 1.</para>
+    <warning>
+      <title>Do not cancel the D-Bus service in a running system</title>
+      <para>The D-Bus service is the message bus for communication between &systemd; clients and the &systemd; manager that is running as PID 1.
+       D-Bus is a stand-alone daemon and an integral part of the init infrastructure.</para>
+
      <para>
-      D-Bus is a stand-alone daemon and an integral part of the init infrastructure.
-      Keep in mind the following properties:
-      </para>
-      <itemizedlist>
-      <listitem>
-      <para>
-      Terminating D-Bus or restarting it in the running system is similar to an attempt to terminate or restart PID 1.
-      </para>
-      </listitem>
-      <listitem>
-      <para>
-      It breaks the &systemd; client and server communication and make most &systemd; functions unusable.
-      </para>
-      </listitem>
-      <listitem>
-      <para>
-      Terminating or restarting D-Bus is neither recommended nor supported.
-      </para>
-      </listitem>
-      <listitem>
-      <para>
-      Updating D-Bus or D-Bus-related packages requires a reboot.
-      You can run <command>sudo zypper ps -s</command> to check if a reboot is required. If D-Bus appears among the listed services, you need to reboot the system.
-      </para>
-      </listitem>
-      </itemizedlist>
-            </important>
-            <para>The <command>systemd-cgls</command> command displays all processes that belong to a &systemd; service.
+      Terminating or restarting the D-Bus service is neither recommended nor supported. This breaks the &systemd; client
+      and server communication and makes most of the &systemd; functions unusable.</para>
+          </warning>
+          <para>The <command>systemd-cgls</command> command displays all processes that belong to a &systemd; service.
               It recursively shows the contents of the specific Linux control group hierarchy in a tree.
               </para>
             <variablelist>

diff --git a/tasks/start-systemd-services.xml b/tasks/start-systemd-services.xml
diff --git a/tasks/systemd-manage-troubleshoot.xml b/tasks/systemd-manage-troubleshoot.xml
@@ -12,7 +12,7 @@
  xmlns:xlink="http://www.w3.org/1999/xlink"
  xmlns:trans="http://docbook.org/ns/transclusion">
   <info>
-    <title>Manage &systemd; troubleshooting</title>
+    <title>Troubleshooting &systemd; management</title>
     <meta name="maintainer" content="[email protected]"/>
   </info>
     <para>