NAME<\/a> systemd-coredump, systemd-coredump.socket, systemd-coredump@.service \u2212 Acquire, save and process core dumps<\/p>\n \/usr\/lib\/systemd\/systemd\u2212coredump<\/p>\n \/usr\/lib\/systemd\/systemd\u2212coredump \u2212\u2212backtrace<\/b><\/p>\n systemd\u2212coredump@.service<\/p>\n systemd\u2212coredump.socket<\/p>\n systemd\u2212coredump@.service is a system service that can acquire core dumps from the kernel and handle them in various ways. The systemd\u2212coredump<\/b> executable does the actual work. It is invoked twice: once as the handler by the kernel, and the second time in the systemd\u2212coredump@.service to actually write the data to the journal.<\/p>\n When the kernel invokes systemd\u2212coredump<\/b> to handle a core dump, it runs in privileged mode, and will connect to the socket created by the systemd\u2212coredump.socket unit, which in turn will spawn an unprivileged systemd\u2212coredump@.service instance to process the core dump. Hence systemd\u2212coredump.socket and systemd\u2212coredump@.service are helper units which do the actual processing of core dumps and are subject to normal service management.<\/p>\n Core dumps can be written to the journal or saved as a file. Once saved they can be retrieved for further processing, for example in gdb<\/b>(1).<\/p>\n By default, systemd\u2212coredump<\/b> 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.<\/p>\n The behavior of a specific program upon reception of a signal is governed by a few factors which are described in detail in core<\/b>(5). In particular, the core dump will only be processed when the related resource limits are sufficient.<\/p>\n It is also possible to invoke systemd\u2212coredump<\/b> with \u2212\u2212backtrace<\/b> option. In this case, systemd\u2212coredump<\/b> expects a journal entry in the journal Journal Export Format<\/font><\/b> [1]<\/font><\/small> on standard input. The entry should contain a MESSAGE=<\/i> field and any additional metadata fields the caller deems reasonable. systemd\u2212coredump<\/b> will append additional metadata fields in the same way it does for core dumps received from the kernel. In this mode, no core dump is stored in the journal.<\/font><\/p>\n For programs started by systemd<\/b> process resource limits can be set by directive LimitCore=<\/i>, see systemd.exec<\/b>(5).<\/font><\/p>\n In order to be used by the kernel to handle core dumps, systemd\u2212coredump<\/b> must be configured in sysctl<\/b>(8) parameter kernel.core_pattern<\/i>. The syntax of this parameter is explained in core<\/b>(5). systemd installs the file \/usr\/lib\/sysctl.d\/50\u2212coredump.conf which configures kernel.core_pattern<\/i> accordingly. This file may be masked or overridden to use a different setting following normal sysctl.d<\/b>(5) rules. If the sysctl configuration is modified, it must be updated in the kernel before it takes effect, see sysctl<\/b>(8) and systemd-sysctl<\/b>(8).<\/font><\/p>\n In order to by used in the \u2212\u2212backtrace<\/b> mode, an appropriate backtrace handler must be installed on the sender side. For example, in case of python<\/b>(1), this means a sys.excepthook<\/i> must installed, see<\/font> systemd\u2212coredump\u2212python<\/font><\/b> [2]<\/font><\/small> .<\/font><\/p>\n The behavior of systemd\u2212coredump<\/b> itself is configured through the configuration file \/etc\/systemd\/coredump.conf and corresponding snippets \/etc\/systemd\/coredump.conf.d\/*.conf, see coredump.conf<\/b>(5). A new instance of systemd\u2212coredump<\/b> is invoked upon receiving every core dump. Therefore, changes in these files will take effect the next time a core dump is received.<\/font><\/p>\n 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\u2212tmpfiles<\/b>, corresponding settings are by default in \/usr\/lib\/tmpfiles.d\/systemd.conf.<\/font><\/p>\n Disabling coredump processing<\/b> Storage=none in coredump.conf<\/b>(5).<\/font><\/p>\n Data stored in the journal can be viewed with journalctl<\/b>(1) as usual. coredumpctl<\/b>(1) can be used to retrieve saved core dumps independent of their location, to display information and to process them e.g. by passing to the GNU debugger (gdb).<\/font><\/p>\n coredump.conf<\/b>(5), coredumpctl<\/b>(1), systemd-journald.service<\/b>(8), systemd-tmpfiles<\/b>(8), core<\/b>(5), sysctl.d<\/b>(5), systemd-sysctl.service<\/b>(8).<\/font><\/p>\n 1.<\/font><\/p>\n<\/td>\n Journal Export Format<\/font><\/p>\n<\/td>\n https:\/\/www.freedesktop.org\/wiki\/Software\/systemd\/export<\/font><\/p>\n 2.<\/font><\/p>\n<\/td>\n systemd-coredump-python<\/font><\/p>\n<\/td>\n https:\/\/github.com\/keszybz\/systemd-coredump-python<\/font><\/p>\n systemd-coredump, systemd-coredump.socket, systemd-coredump@.service \u2212 Acquire, save and process core dumps <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[5,52,4,427],"class_list":["post-3294","post","type-post","status-publish","format-standard","hentry","category-8-administracion-del-sistema","tag-5","tag-administracion","tag-man8","tag-systemd-coredump"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3294","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=3294"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3294\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=3294"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=3294"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=3294"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
SYNOPSIS<\/a>
DESCRIPTION<\/a>
CONFIGURATION<\/a>
USAGE<\/a>
SEE ALSO<\/a>
NOTES<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
CONFIGURATION <\/a> <\/h2>\n
To disable potentially resource\u2212intensive processing by systemd\u2212coredump<\/b>, set<\/font><\/p>\n
ProcessSizeMax=0<\/font><\/p>\nUSAGE <\/a> <\/h2>\n
SEE ALSO <\/a> <\/h2>\n
NOTES <\/a> <\/h2>\n
\n
\n <\/td>\n \n <\/td>\n \n <\/td>\n<\/tr>\n<\/table>\n \n
\n <\/td>\n \n <\/td>\n \n <\/td>\n<\/tr>\n<\/table>\n
\n","protected":false},"excerpt":{"rendered":"