From c6ef002b80b3334e770a50e5eb9bae93a716da68 Mon Sep 17 00:00:00 2001 From: AJ Jordan Date: Mon, 14 Dec 2020 15:35:43 -0800 Subject: [PATCH] man: clarify that coredumps are gc'd after 3 days --- man/systemd-coredump.xml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/man/systemd-coredump.xml b/man/systemd-coredump.xml index 4ac6de1ee2..f92cfd55ea 100644 --- a/man/systemd-coredump.xml +++ b/man/systemd-coredump.xml @@ -53,7 +53,8 @@ By default, systemd-coredump will log the core dump including a backtrace if possible to the journal and store the core dump itself in an external file in - /var/lib/systemd/coredump. + /var/lib/systemd/coredump. These core dumps are deleted after a few days by + default; see /usr/lib/tmpfiles.d/systemd.conf for details. The behavior of a specific program upon reception of a signal is governed by a few factors which are described in detail in @@ -111,7 +112,8 @@ Resources used by core dump files are restricted in two ways. Parameters like maximum size of acquired core dumps and files can be set in files /etc/systemd/coredump.conf and snippets mentioned above. In addition the storage time of core dump files is restricted by systemd-tmpfiles, - corresponding settings are by default in /usr/lib/tmpfiles.d/systemd.conf. + corresponding settings are by default in /usr/lib/tmpfiles.d/systemd.conf. The default is + to delete core dumps after a few days; see the above file for details. Disabling coredump processing