shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2024-12-22 13:33:56 +03:00
Code

man: clarify what is inside/outside the container in coredump info

Browse Source
This commit is contained in:
Zbigniew Jędrzejewski-Szmek 2021-03-01 20:30:40 +01:00
parent a1174b2260
commit 40019c32d7
1 changed files with 36 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

41
man/systemd-coredump.xml
View File

@ -178,7 +178,12 @@ COREDUMP_FILENAME=/var/lib/systemd/coredump/core.Web….552351.….zst
<term><varname>COREDUMP_UID=</varname></term>
<term><varname>COREDUMP_PID=</varname></term>
<term><varname>COREDUMP_GID=</varname></term>
<listitem><para>The process number (PID) and owner (UID and GID) of the crashed process.</para>
<listitem><para>The process number (PID), owner user number (UID), and group number (GID) of the
crashed process.</para>
<para>When the crashed process was part of a container (or in a process or user namespace in
general), those are the values as seen <emphasis>outside</emphasis>, in the namespace where
<filename>systemd-coredump</filename> is running.</para>
</listitem>
</varlistentry>
@ -199,6 +204,9 @@ COREDUMP_FILENAME=/var/lib/systemd/coredump/core.Web….552351.….zst
<term><varname>COREDUMP_UNIT=</varname></term>
<term><varname>COREDUMP_SLICE=</varname></term>
<listitem><para>The system unit and slice names.</para>
<para>When the crashed process was in container, those are the units names
<emphasis>outside</emphasis>, in the main system manager.</para>
</listitem>
</varlistentry>
@ -207,7 +215,11 @@ COREDUMP_FILENAME=/var/lib/systemd/coredump/core.Web….552351.….zst
<listitem><para>Control group information in the format used in
<filename>/proc/self/cgroup</filename>. On systems with the unified cgroup hierarchy, this is a
single path prefixed with <literal>0::</literal>, and multiple paths prefixed with controller numbers
on legacy systems.</para></listitem>
on legacy systems.</para>
<para>When the crashed process was in a container, this is the full path, as seen outside of the
container.</para>
</listitem>
</varlistentry>
<varlistentry>
@ -215,7 +227,11 @@ COREDUMP_FILENAME=/var/lib/systemd/coredump/core.Web….552351.….zst
<term><varname>COREDUMP_USER_UNIT=</varname></term>
<listitem><para>The numerical UID of the user owning the login session or systemd user unit of the
crashed process, and the user manager unit. Both fields are only present for user processes.
</para></listitem>
</para>
<para>When the crashed process was in container, those are the values <emphasis>outside</emphasis>,
in the main system.</para>
</listitem>
</varlistentry>
<varlistentry>
@ -232,6 +248,9 @@ COREDUMP_FILENAME=/var/lib/systemd/coredump/core.Web….552351.….zst
<term><varname>COREDUMP_ROOT=</varname></term>
<listitem><para>The current working directory and root directory of the crashed process.</para>
<para>When the crashed process is in a container, those paths are relative to the root of the
container's mount namespace.</para>
</listitem>
</varlistentry>
@ -257,8 +276,17 @@ flags: ...
</varlistentry>
<varlistentry>
<term><varname>COREDUMP_COMM=</varname></term>
<term><varname>COREDUMP_EXE=</varname></term>
<listitem><para>The destination of the <filename>/proc/<replaceable>pid</replaceable>/exe</filename>
symlink.</para>
<para>When the crashed process is in a container, that path is relative to the root of the
container's mount namespace.</para></listitem>
</varlistentry>
<varlistentry>
<term><varname>COREDUMP_COMM=</varname></term>
<term><varname>COREDUMP_PROC_STATUS=</varname></term>
<term><varname>COREDUMP_PROC_MAPS=</varname></term>
<term><varname>COREDUMP_PROC_LIMITS=</varname></term>
@ -284,7 +312,10 @@ flags: ...
<varlistentry>
<term><varname>COREDUMP_HOSTNAME=</varname></term>
<listitem><para>The system hostname.</para></listitem>
<listitem><para>The system hostname.</para>
<para>When the crashed process was in container, this is the container hostname.</para>
</listitem>
</varlistentry>
<varlistentry>