mirror of
https://github.com/systemd/systemd.git
synced 2024-12-11 19:23:37 +08:00
cf677ac1b7
This sounds overly low-level and implementation-detaily. Let's just use the default level XZ suggests. This gives us more room to possibly swap out the compression algorithm used, as the compression level range will not leak into user configuration.
146 lines
5.3 KiB
XML
146 lines
5.3 KiB
XML
<?xml version='1.0'?> <!--*-nxml-*-->
|
|
<?xml-stylesheet type="text/xsl" href="http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl"?>
|
|
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
|
|
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
|
|
|
|
<!--
|
|
This file is part of systemd.
|
|
|
|
Copyright 2014 Zbigniew Jędrzejewski-Szmek
|
|
|
|
systemd is free software; you can redistribute it and/or modify it
|
|
under the terms of the GNU Lesser General Public License as published by
|
|
the Free Software Foundation; either version 2.1 of the License, or
|
|
(at your option) any later version.
|
|
|
|
systemd is distributed in the hope that it will be useful, but
|
|
WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
|
Lesser General Public License for more details.
|
|
|
|
You should have received a copy of the GNU Lesser General Public License
|
|
along with systemd; If not, see <http://www.gnu.org/licenses/>.
|
|
-->
|
|
|
|
<refentry id="coredump.conf" conditional="ENABLE_COREDUMP">
|
|
<refentryinfo>
|
|
<title>coredump.conf</title>
|
|
<productname>systemd</productname>
|
|
|
|
<authorgroup>
|
|
<author>
|
|
<contrib>Developer</contrib>
|
|
<firstname>Lennart</firstname>
|
|
<surname>Poettering</surname>
|
|
<email>lennart@poettering.net</email>
|
|
</author>
|
|
</authorgroup>
|
|
</refentryinfo>
|
|
|
|
<refmeta>
|
|
<refentrytitle>coredump.conf</refentrytitle>
|
|
<manvolnum>5</manvolnum>
|
|
</refmeta>
|
|
|
|
<refnamediv>
|
|
<refname>coredump.conf</refname>
|
|
<refpurpose>Coredump storage configuration file</refpurpose>
|
|
</refnamediv>
|
|
|
|
<refsynopsisdiv>
|
|
<para><filename>/etc/systemd/coredump.conf</filename></para>
|
|
</refsynopsisdiv>
|
|
|
|
<refsect1>
|
|
<title>Description</title>
|
|
|
|
<para>This file configures the behaviour of <command>systemd-coredump</command>,
|
|
a handler for core dumps invoked by the kernel.</para>
|
|
</refsect1>
|
|
|
|
<refsect1>
|
|
<title>Options</title>
|
|
|
|
<para>All options are configured in the
|
|
<literal>[Coredump]</literal> section:</para>
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
|
<term><varname>Storage=</varname></term>
|
|
|
|
<listitem><para>Controls where to store cores. One of
|
|
<literal>none</literal>, <literal>external</literal>,
|
|
<literal>journal</literal>, and <literal>both</literal>. When
|
|
<literal>none</literal> the coredumps will be logged but not
|
|
stored permanently. When <literal>external</literal> (the
|
|
default), cores will be stored in <filename>/var/lib/systemd/coredump</filename>.
|
|
When <literal>journal</literal>, cores will be stored in
|
|
the journal and rotated following normal journal
|
|
rotation patterns. When <literal>both</literal>, cores
|
|
will be stored in both locations.</para>
|
|
|
|
<para>When cores are stored in the journal, they might be
|
|
compressed following journal compression settings, see
|
|
<citerefentry><refentrytitle>journald.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
|
|
When cores are stored externally, they will be compressed
|
|
by default, see below.</para></listitem>
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
<term><varname>Compression=</varname></term>
|
|
|
|
<listitem><para>Controls the type of compression for external
|
|
storage. One of <literal>xz</literal> or
|
|
<literal>none</literal>.</para>
|
|
</listitem>
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
<term><varname>ProcessSizeMax=</varname></term>
|
|
|
|
<listitem><para>The maximum size in bytes of a core
|
|
which will be processed. Coredumps exceeding this size
|
|
will be logged, but the backtrace will not be generated
|
|
and the core will not be stored.</para></listitem>
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
<term><varname>ExternalSizeMax=</varname></term>
|
|
<term><varname>JournalSizeMax=</varname></term>
|
|
|
|
<listitem><para>The maximum (uncompressed) size in bytes of a
|
|
core to be saved.</para></listitem>
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
<term><varname>MaxUse=</varname></term>
|
|
<term><varname>KeepFree=</varname></term>
|
|
|
|
<listitem><para>Enforce limits on the disk space taken up by
|
|
externally stored coredumps. <option>MaxUse=</option> makes
|
|
sure that old coredumps are removed as soon as the total disk
|
|
space taken up by coredumps grows beyond this limit (defaults
|
|
to 10% of the total disk size). <option>KeepFree=</option>
|
|
controls how much disk space to keep free at least (defaults
|
|
to 15% of the total disk size). Note that the disk space used
|
|
by coredumps might temporarily exceed these limits while
|
|
coredumps are processed. Note that old coredumps are also
|
|
removed based on on time via
|
|
<citerefentry><refentrytitle>systemd-tmpfiles</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para></listitem>
|
|
</varlistentry>
|
|
</variablelist>
|
|
|
|
</refsect1>
|
|
|
|
<refsect1>
|
|
<title>See Also</title>
|
|
<para>
|
|
<citerefentry><refentrytitle>systemd-journald.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
|
|
<citerefentry><refentrytitle>coredumpctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
|
|
<citerefentry><refentrytitle>systemd-tmpfiles</refentrytitle><manvolnum>8</manvolnum></citerefentry>
|
|
</para>
|
|
</refsect1>
|
|
|
|
</refentry>
|