shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-01-12 13:18:14 +03:00
Code

man: document what happens if --kill-signal= is not used in nspawn and --boot neither

Browse Source
This commit is contained in:
Lennart Poettering 2018-05-07 17:51:33 +02:00
parent c7fc3c4cfe
commit 1752d69a8b
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
man/systemd-nspawn.xml
View File

@ -737,13 +737,13 @@
<varlistentry> <varlistentry>
<term><option>--kill-signal=</option></term> <term><option>--kill-signal=</option></term>
<listitem><para>Specify the process signal to send to the <listitem><para>Specify the process signal to send to the container's PID 1 when nspawn itself receives
container's PID 1 when nspawn itself receives SIGTERM, in <constant>SIGTERM</constant>, in order to trigger an orderly shutdown of the container. Defaults to
order to trigger an orderly shutdown of the <constant>SIGRTMIN+3</constant> if <option>--boot</option> is used (on systemd-compatible init systems
container. Defaults to SIGRTMIN+3 if <option>--boot</option> <constant>SIGRTMIN+3</constant> triggers an orderly shutdown). If <option>--boot</option> is not used and this
is used (on systemd-compatible init systems SIGRTMIN+3 option is not specified the container's processes are terminated abrubtly via <constant>SIGKILL</constant>. For
triggers an orderly shutdown). For a list of valid signals, see a list of valid signals, see <citerefentry
<citerefentry project='man-pages'><refentrytitle>signal</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para></listitem> project='man-pages'><refentrytitle>signal</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para></listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>