lxc-kill man update about SIGSTOP and SIGKILL

Signed-off-by: Michel Normand <normand@fr.ibm.com>
Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

diff --git a/doc/lxc-kill.sgml.in b/doc/lxc-kill.sgml.in
index c3373c6fad26d216768c89f932e0f746667948bc..2b06ab866cb9b30dad592e7a72b3c777185c8cca 100644 (file)
--- a/doc/lxc-kill.sgml.in
+++ b/doc/lxc-kill.sgml.in
@@ -42,11 +42,17 @@
       the <replaceable>SIGNUM</replaceable> signal to the first process of the container.
     </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
        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
        lxc-execute (1).
+       Obviously the SIGKILL and SIGSTOP signals are not able to be forwarded,
+       (as per the signal(7) man page).
     </para>
   </refsect1>