Skip to content

L
lxc
Commit b8da590f by Michel Normand Committed by Daniel Lezcano
Options

lxc-kill man update about SIGSTOP and SIGKILL

Signed-off-by: 's avatarMichel Normand <normand@fr.ibm.com> Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
parent d0817ec9
Showing with 6 additions and 0 deletions
doc/lxc-kill.sgml.in
...@@ -43,10 +43,16 @@ ...@@ -43,10 +43,16 @@
</para> </para>
<para> <para>
The <replaceable>SIGNUM</replaceable> is a numeric value,
the signal name is not supported.
</para>
<para>
If this command is used on an application container ran by If this command is used on an application container ran by
lxc-execute, the lxc-init will receive the signal and will forward it to lxc-execute, the lxc-init will receive the signal and will forward it to
the process 2 which is the command specified in the command line. See the process 2 which is the command specified in the command line. See
lxc-execute (1). lxc-execute (1).
Obviously the SIGKILL and SIGSTOP signals are not able to be forwarded,
(as per the signal(7) man page).
</para> </para>
</refsect1> </refsect1>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment