diff options
author | Michal Sekletar <msekleta@redhat.com> | 2024-07-09 15:21:34 +0200 |
---|---|---|
committer | Luca Boccassi <luca.boccassi@gmail.com> | 2024-08-06 18:32:42 +0200 |
commit | 68511cebe58977ea68ae4f57c6462e979efd1cff (patch) | |
tree | 9fb9445b00cd0b8f810dbb24220fc1e52043dc90 /man/coredump.conf.xml | |
parent | sysusers: check if requested group name matches user name in queue (diff) | |
download | systemd-68511cebe58977ea68ae4f57c6462e979efd1cff.tar.xz systemd-68511cebe58977ea68ae4f57c6462e979efd1cff.zip |
coredump: generate properly symbolized stacktrace for containerized processes
Diffstat (limited to 'man/coredump.conf.xml')
-rw-r--r-- | man/coredump.conf.xml | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/man/coredump.conf.xml b/man/coredump.conf.xml index 2eedf942c0..65772d84d7 100644 --- a/man/coredump.conf.xml +++ b/man/coredump.conf.xml @@ -110,6 +110,21 @@ </varlistentry> <varlistentry> + <term><varname>AccessContainer=</varname></term> + + <listitem><para>Controls whether <command>systemd-coredump</command> will attempt to use the mount tree of + a process that crashed within a container. Access to the container's filesystem might be necessary to generate + a fully symbolized backtrace. If set to <literal>yes</literal>, then <command>systemd-coredump</command> will + obtain the mount tree from corresponding mount namespace and will try to generate the stack trace using the + binary and libraries from the mount namespace. Note that the coredump of the containerized process might + still be saved in <filename>/var/lib/systemd/coredump/</filename> even if <varname>AccessContainer=</varname> + is set to <literal>no</literal>. Defaults to <literal>no</literal>.</para> + + <xi:include href="version-info.xml" xpointer="v257"/> + </listitem> + </varlistentry> + + <varlistentry> <term><varname>ExternalSizeMax=</varname></term> <term><varname>JournalSizeMax=</varname></term> |