summaryrefslogtreecommitdiff
path: root/man/coredump.conf.xml
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2014-06-27 19:04:31 +0200
committerLennart Poettering <lennart@poettering.net>2014-06-27 19:35:57 +0200
commitcf677ac1b7ae1e46c593d055df27f36528be548a (patch)
tree6e572b62e688dd303d5406956e5b06beba8bdf9c /man/coredump.conf.xml
parent168562d7ed8fcfc4612e51d221e7a5fa1e1297b5 (diff)
downloadsystemd-cf677ac1b7ae1e46c593d055df27f36528be548a.tar.gz
coredump: don't expose the compression level as configuration option
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.
Diffstat (limited to 'man/coredump.conf.xml')
-rw-r--r--man/coredump.conf.xml9
1 files changed, 0 insertions, 9 deletions
diff --git a/man/coredump.conf.xml b/man/coredump.conf.xml
index e24d958ac4..cc54466771 100644
--- a/man/coredump.conf.xml
+++ b/man/coredump.conf.xml
@@ -97,15 +97,6 @@
</varlistentry>
<varlistentry>
- <term><varname>CompressionLevel=</varname></term>
-
- <listitem><para>Controls the level of compression for external
- storage. An integer between 0 and 9. See
- <citerefentry><refentrytitle>xz</refentrytitle><manvolnum>1</manvolnum></citerefentry>
- for more details.</para></listitem>
- </varlistentry>
-
- <varlistentry>
<term><varname>ProcessSizeMax=</varname></term>
<listitem><para>The maximum size in bytes of a core