- Timestamp:
- 03/31/2021 10:41:37 AM (3 years ago)
- Branches:
- ml-11.0, multilib
- Children:
- d4248df
- Parents:
- 6fc519e
- git-author:
- Thomas Trepl <thomas@…> (03/15/2020 10:56:46 AM)
- git-committer:
- Xℹ Ruoyao <xry111@…> (03/31/2021 10:41:37 AM)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter07/systemd-custom.xml
r6fc519e rc7e74d6 208 208 </itemizedlist> 209 209 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 247 cat > /etc/systemd/coredump.conf.d/maxuse.conf << EOF 248 <literal>[Coredump] 249 MaxUse=5G</literal> 250 EOF</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> 210 256 </sect2> 211 257
Note:
See TracChangeset
for help on using the changeset viewer.