Changeset 4d796ca

Timestamp:

03/14/2020 07:10:05 AM (4 years ago)

Author:

Xi Ruoyao <xry111@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

8671978

Parents:

6fb1004

Message:

systemd-custom: add a section discussing core dumps

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@11781 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:

• chapter07/systemd-custom.xml (modified) (1 diff)

chapter07/systemd-custom.xml

@@ -208 +208 @@
     </itemizedlist>
 
+  </sect2>
+
+  <sect2>
+    <title>Working with Core Dumps</title>
+
+    <para>Core dumps are useful to debug crashed programs, especially
+    when a daemon process crashes. On systemd booted systems the core
+    dumping is handled by <command>systemd-coredump</command>.  It will
+    log the core dump into the journal and store the core dump itself in
+    <filename class="directory">/var/lib/systemd/coredump</filename>.
+    To retrieve and process core dumps, <command>coredumpctl</command>
+    tool is provided.  Here are some examples of frequently used commands:
+    </para>
+
+    <itemizedlist>
+      <listitem>
+        <para><command>coredumpctl -r</command>: lists all core dumps in
+        reversed chronological order.</para>
+      </listitem>
+      <listitem>
+        <para><command>coredumpctl -1 info</command>: show the information
+        of the last core dump.</para>
+      </listitem>
+      <listitem>
+        <para><command>coredumpctl -1 debug</command>: load the last core
+        dump into <ulink url="&blfs-book;general/gdb.html">GDB</ulink>.
+        </para>
+      </listitem>
+    </itemizedlist>
+
+    <para>Core dumps may use a lot of disk space.  The maximum disk space
+    used by core dumps can be limited by creating a configuration file in
+    <filename class="directory">/etc/systemd/coredump.conf.d</filename>.
+    For example:</para>
+
+<screen role="nodump"><userinput>mkdir -pv /etc/systemd/coredump.conf.d
+
+cat &gt; /etc/systemd/coredump.conf.d/maxuse.conf &lt;&lt; EOF
+<literal>[Coredump]
+MaxUse=5G</literal>
+EOF</userinput></screen>
+
+    <para>See <filename>systemd-coredump(8)</filename>,
+    <filename>coredumpctl(1)</filename>, and
+    <filename>coredump.conf.d(5)</filename> manual pages for more
+    information.</para>
   </sect2>