1
0
mirror of https://github.com/systemd/systemd synced 2025-10-03 10:44:44 +02:00

Compare commits

..

No commits in common. "ebf7472569805b361593b6ec6817b00880244e8a" and "cd18afec16bf179205a1d4fb371af8546d3e14f3" have entirely different histories.

5 changed files with 34 additions and 60 deletions

View File

@ -288,16 +288,8 @@ installed systemd tests:
`systemd-tmpfiles`: `systemd-tmpfiles`:
* `SYSTEMD_TMPFILES_FORCE_SUBVOL` if unset, `v`/`q`/`Q` lines will create * `SYSTEMD_TMPFILES_FORCE_SUBVOL` - if unset, `v`/`q`/`Q` lines will create
subvolumes only if the OS itself is installed into a subvolume. If set to `1` subvolumes only if the OS itself is installed into a subvolume. If set to `1`
(or another value interpreted as true), these lines will always create (or another value interpreted as true), these lines will always create
subvolumes if the backing filesystem supports them. If set to `0`, these subvolumes if the backing filesystem supports them. If set to `0`, these
lines will always create directories. lines will always create directories.
`systemd-sysv-generator`:
* `$SYSTEMD_SYSVINIT_PATH` — Controls where `systemd-sysv-generator` looks for
SysV init scripts.
* `$SYSTEMD_SYSVRCND_PATH` — Controls where `systemd-sysv-generator` looks for
SysV init script runlevel link farms.

View File

@ -115,7 +115,7 @@
handler must be installed on the sender side. For example, in case of handler must be installed on the sender side. For example, in case of
<citerefentry project='die-net'><refentrytitle>python</refentrytitle><manvolnum>1</manvolnum></citerefentry>, this <citerefentry project='die-net'><refentrytitle>python</refentrytitle><manvolnum>1</manvolnum></citerefentry>, this
means a <varname>sys.excepthook</varname> must be installed, see means a <varname>sys.excepthook</varname> must be installed, see
<ulink url="https://github.com/systemd/systemd-coredump-python">systemd-coredump-python</ulink>. <ulink url="https://github.com/keszybz/systemd-coredump-python">systemd-coredump-python</ulink>.
</para> </para>
<para>The behavior of <command>systemd-coredump</command> itself is configured through the configuration file <para>The behavior of <command>systemd-coredump</command> itself is configured through the configuration file
@ -178,12 +178,7 @@ COREDUMP_FILENAME=/var/lib/systemd/coredump/core.Web….552351.….zst
<term><varname>COREDUMP_UID=</varname></term> <term><varname>COREDUMP_UID=</varname></term>
<term><varname>COREDUMP_PID=</varname></term> <term><varname>COREDUMP_PID=</varname></term>
<term><varname>COREDUMP_GID=</varname></term> <term><varname>COREDUMP_GID=</varname></term>
<listitem><para>The process number (PID), owner user number (UID), and group number (GID) of the <listitem><para>The process number (PID) and owner (UID and GID) of the crashed process.</para>
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> </listitem>
</varlistentry> </varlistentry>
@ -204,9 +199,6 @@ COREDUMP_FILENAME=/var/lib/systemd/coredump/core.Web….552351.….zst
<term><varname>COREDUMP_UNIT=</varname></term> <term><varname>COREDUMP_UNIT=</varname></term>
<term><varname>COREDUMP_SLICE=</varname></term> <term><varname>COREDUMP_SLICE=</varname></term>
<listitem><para>The system unit and slice names.</para> <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> </listitem>
</varlistentry> </varlistentry>
@ -215,11 +207,7 @@ COREDUMP_FILENAME=/var/lib/systemd/coredump/core.Web….552351.….zst
<listitem><para>Control group information in the format used in <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 <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 single path prefixed with <literal>0::</literal>, and multiple paths prefixed with controller numbers
on legacy systems.</para> on legacy systems.</para></listitem>
<para>When the crashed process was in a container, this is the full path, as seen outside of the
container.</para>
</listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
@ -227,11 +215,7 @@ COREDUMP_FILENAME=/var/lib/systemd/coredump/core.Web….552351.….zst
<term><varname>COREDUMP_USER_UNIT=</varname></term> <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 <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. crashed process, and the user manager unit. Both fields are only present for user processes.
</para> </para></listitem>
<para>When the crashed process was in container, those are the values <emphasis>outside</emphasis>,
in the main system.</para>
</listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
@ -248,9 +232,6 @@ COREDUMP_FILENAME=/var/lib/systemd/coredump/core.Web….552351.….zst
<term><varname>COREDUMP_ROOT=</varname></term> <term><varname>COREDUMP_ROOT=</varname></term>
<listitem><para>The current working directory and root directory of the crashed process.</para> <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> </listitem>
</varlistentry> </varlistentry>
@ -275,18 +256,9 @@ flags: ...
</para></listitem> </para></listitem>
</varlistentry> </varlistentry>
<varlistentry>
<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> <varlistentry>
<term><varname>COREDUMP_COMM=</varname></term> <term><varname>COREDUMP_COMM=</varname></term>
<term><varname>COREDUMP_EXE=</varname></term>
<term><varname>COREDUMP_PROC_STATUS=</varname></term> <term><varname>COREDUMP_PROC_STATUS=</varname></term>
<term><varname>COREDUMP_PROC_MAPS=</varname></term> <term><varname>COREDUMP_PROC_MAPS=</varname></term>
<term><varname>COREDUMP_PROC_LIMITS=</varname></term> <term><varname>COREDUMP_PROC_LIMITS=</varname></term>
@ -312,10 +284,7 @@ flags: ...
<varlistentry> <varlistentry>
<term><varname>COREDUMP_HOSTNAME=</varname></term> <term><varname>COREDUMP_HOSTNAME=</varname></term>
<listitem><para>The system hostname.</para> <listitem><para>The system hostname.</para></listitem>
<para>When the crashed process was in container, this is the container hostname.</para>
</listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>

View File

@ -60,6 +60,20 @@
<citerefentry><refentrytitle>systemd.generator</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para> <citerefentry><refentrytitle>systemd.generator</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para>
</refsect1> </refsect1>
<refsect1>
<title>Environment</title>
<para>Special variables understood by <command>systemd-sysv-generator</command>:</para>
<variablelist class='environment-variables'>
<varlistentry>
<term><varname>$SYSTEMD_SYSVINIT_PATH</varname></term>
<listitem><para>Controls where systemd looks for SysV init scripts.</para></listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1> <refsect1>
<title>See Also</title> <title>See Also</title>
<para> <para>

View File

@ -136,14 +136,14 @@ KeyThree=value 3\
single quotes ('…') may be used to wrap a whole item (the opening quote may appear only at the beginning single quotes ('…') may be used to wrap a whole item (the opening quote may appear only at the beginning
or after whitespace that is not quoted, and the closing quote must be followed by whitespace or the end or after whitespace that is not quoted, and the closing quote must be followed by whitespace or the end
of line), in which case everything until the next matching quote becomes part of the same item. Quotes of line), in which case everything until the next matching quote becomes part of the same item. Quotes
themselves are removed. C-style escapes are supported. The table below contains the list of known escape themselves are removed. C-style escapes are also supported. The table below contains the list of known
patterns. Only escape patterns which match the syntax in the table are allowed; other patterns may be escape patterns. Only escape patterns which match the syntax in the table are allowed; other patterns may
added in the future and unknown patterns will result in a warning. In particular, any backslashes should be added in the future and unknown patterns will result in a warning. In particular, any backslashes
be doubled. Finally, a trailing backslash (<literal>\</literal>) may be used to merge lines, as described should be doubled. Finally, a trailing backslash (<literal>\</literal>) may be used to merge lines, as
above. UTF-8 is accepted, and hence typical unicode characters do not need to be escaped.</para> described above.</para>
<table> <table>
<title>Supported escapes</title> <title>Supported C escapes</title>
<tgroup cols='2'> <tgroup cols='2'>
<colspec colname='escape' /> <colspec colname='escape' />
<colspec colname='meaning' /> <colspec colname='meaning' />
@ -206,14 +206,6 @@ KeyThree=value 3\
<entry><literal>\<replaceable>nnn</replaceable></literal></entry> <entry><literal>\<replaceable>nnn</replaceable></literal></entry>
<entry>character number <replaceable>nnn</replaceable> in octal encoding</entry> <entry>character number <replaceable>nnn</replaceable> in octal encoding</entry>
</row> </row>
<row>
<entry><literal>\u<replaceable>nnnn</replaceable></literal></entry>
<entry>unicode code point <replaceable>nnnn</replaceable> in hexadecimal encoding</entry>
</row>
<row>
<entry><literal>\U<replaceable>nnnnnnnn</replaceable></literal></entry>
<entry>unicode code point <replaceable>nnnnnnnn</replaceable> in hexadecimal encoding</entry>
</row>
</tbody> </tbody>
</tgroup> </tgroup>
</table> </table>

View File

@ -696,6 +696,13 @@
</para></listitem> </para></listitem>
</varlistentry> </varlistentry>
<varlistentry>
<term><varname>$SYSTEMD_SYSVRCND_PATH</varname></term>
<listitem><para>Controls where systemd looks for SysV init
script runlevel link farms.</para></listitem>
</varlistentry>
<xi:include href="common-variables.xml" xpointer="pager"/> <xi:include href="common-variables.xml" xpointer="pager"/>
<xi:include href="common-variables.xml" xpointer="less"/> <xi:include href="common-variables.xml" xpointer="less"/>
<xi:include href="common-variables.xml" xpointer="lesscharset"/> <xi:include href="common-variables.xml" xpointer="lesscharset"/>