From b8da590f0e90f70baa2c29488db554d55507db0d Mon Sep 17 00:00:00 2001 From: Michel Normand Date: Thu, 27 May 2010 14:26:09 +0200 Subject: [PATCH] lxc-kill man update about SIGSTOP and SIGKILL Signed-off-by: Michel Normand Signed-off-by: Daniel Lezcano --- doc/lxc-kill.sgml.in | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/doc/lxc-kill.sgml.in b/doc/lxc-kill.sgml.in index c3373c6fa..2b06ab866 100644 --- a/doc/lxc-kill.sgml.in +++ b/doc/lxc-kill.sgml.in @@ -42,11 +42,17 @@ the SIGNUM signal to the first process of the container. + + The SIGNUM is a numeric value, + the signal name is not supported. + 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).