Changeset 4d796ca


Ignore:
Timestamp:
03/14/2020 07:10:05 AM (21 months 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, cross-chap5, ml-11.0, multilib, old-trunk, trunk, xry111/git-transition, xry111/glibc-2.34, xry111/tester-nohack, xry111/usr-move
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:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter07/systemd-custom.xml

    r6fb1004 r4d796ca  
    208208    </itemizedlist>
    209209
     210  </sect2>
     211
     212  <sect2>
     213    <title>Working with Core Dumps</title>
     214
     215    <para>Core dumps are useful to debug crashed programs, especially
     216    when a daemon process crashes. On systemd booted systems the core
     217    dumping is handled by <command>systemd-coredump</command>.  It will
     218    log the core dump into the journal and store the core dump itself in
     219    <filename class="directory">/var/lib/systemd/coredump</filename>.
     220    To retrieve and process core dumps, <command>coredumpctl</command>
     221    tool is provided.  Here are some examples of frequently used commands:
     222    </para>
     223
     224    <itemizedlist>
     225      <listitem>
     226        <para><command>coredumpctl -r</command>: lists all core dumps in
     227        reversed chronological order.</para>
     228      </listitem>
     229      <listitem>
     230        <para><command>coredumpctl -1 info</command>: show the information
     231        of the last core dump.</para>
     232      </listitem>
     233      <listitem>
     234        <para><command>coredumpctl -1 debug</command>: load the last core
     235        dump into <ulink url="&blfs-book;general/gdb.html">GDB</ulink>.
     236        </para>
     237      </listitem>
     238    </itemizedlist>
     239
     240    <para>Core dumps may use a lot of disk space.  The maximum disk space
     241    used by core dumps can be limited by creating a configuration file in
     242    <filename class="directory">/etc/systemd/coredump.conf.d</filename>.
     243    For example:</para>
     244
     245<screen role="nodump"><userinput>mkdir -pv /etc/systemd/coredump.conf.d
     246
     247cat &gt; /etc/systemd/coredump.conf.d/maxuse.conf &lt;&lt; EOF
     248<literal>[Coredump]
     249MaxUse=5G</literal>
     250EOF</userinput></screen>
     251
     252    <para>See <filename>systemd-coredump(8)</filename>,
     253    <filename>coredumpctl(1)</filename>, and
     254    <filename>coredump.conf.d(5)</filename> manual pages for more
     255    information.</para>
    210256  </sect2>
    211257
Note: See TracChangeset for help on using the changeset viewer.