]> git.proxmox.com Git - systemd.git/blame - man/systemd-coredump.8
Imported Upstream version 218
[systemd.git] / man / systemd-coredump.8
CommitLineData
5eef597e 1'\" t
f47781d8 2.TH "SYSTEMD\-COREDUMP" "8" "" "systemd 218" "systemd-coredump"
5eef597e
MP
3.\" -----------------------------------------------------------------
4.\" * Define some portability stuff
5.\" -----------------------------------------------------------------
6.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
7.\" http://bugs.debian.org/507673
8.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
9.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10.ie \n(.g .ds Aq \(aq
11.el .ds Aq '
12.\" -----------------------------------------------------------------
13.\" * set default formatting
14.\" -----------------------------------------------------------------
15.\" disable hyphenation
16.nh
17.\" disable justification (adjust text to left margin only)
18.ad l
19.\" -----------------------------------------------------------------
20.\" * MAIN CONTENT STARTS HERE *
21.\" -----------------------------------------------------------------
22.SH "NAME"
23systemd-coredump \- Log and store core dumps
24.SH "SYNOPSIS"
25.PP
26/usr/lib/systemd/systemd\-coredump
27.SH "DESCRIPTION"
28.PP
29\fBsystemd\-coredump\fR
30can be used as a helper binary by the kernel when a user space program receives a fatal signal and dumps core\&. For it to be used in this capacity, it must be specified by the
31\fIkernel\&.core_pattern\fR\ \&\fBsysctl\fR(8)
32setting\&. Systemd installs
33/usr/lib/sysctl\&.d/50\-coredump\&.conf
34which configures
35\fIkernel\&.core_pattern\fR
36to invoke
37\fBsystemd\-coredump\fR\&. This file may be masked or overriden to use a different setting following normal
38\fBsysctl.d\fR(5)
39rules\&.
40.PP
41The behaviour of a specific program upon reception of a signal is governed by a few factors which are described in detail in
42\fBcore\fR(5)\&. In particular, the coredump will only be processed when the related resource limits are high enough\&. For programs started by
43\fBsystemd\fR
44those may be set using
45\fILimitCore=\fR
46(see
47\fBsystemd.exec\fR(5))\&.
48.PP
49\fBsystemd\-coredump\fR
50will log the coredump including a backtrace if possible, and store the core (contents of process\*(Aq memory contents) in an external file on disk in
51/var/lib/systemd/coredump, or directly in the journal\&. This behaviour may be modified using
52\fBcoredump.conf\fR(5)\&.
53.PP
54Apart from the
55\fBjournalctl\fR(1)
56log viewer,
57\fBcoredumpctl\fR(1)
58may be used to list and extract coredumps\&.
59.SH "SEE ALSO"
60.PP
61\fBcoredump.conf\fR(5),
62\fBcoredumpctl\fR(1),
63\fBsystemd-journald.service\fR(8),
64\fBcore\fR(5),
65\fBsysctl.d\fR(5),
66\fBsystemd-sysctl.service\fR(8)\&.