1
.\" This manpage has been automatically generated by docbook2man
2
.\" from a DocBook document. This tool can be found at:
3
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
4
.\" Please send any bug reports, improvements, comments, patches,
5
.\" etc. to Steve Cheng <steve@ggi-project.org>.
6
.TH "LXC-KILL" "1" "24 June 2010" "IBM" ""
9
lxc-kill \- Send a signal to the process 1 of the container.
12
\fBlxc-kill --name=\fINAME\fB \fISIGNUM\fB\fR
17
the \fISIGNUM\fR signal to the first process of the container.
19
The \fISIGNUM\fR is a numeric value,
20
the signal name is not supported.
22
If this command is used on an application container ran by
23
lxc-execute, the lxc-init will receive the signal and will forward it to
24
the process 2 which is the command specified in the command line. See
26
Obviously the SIGKILL and SIGSTOP signals are not able to be forwarded,
27
(as per the signal(7) man page).
30
These options are common to most of lxc commands.
33
Print a longer usage message than normal.
36
Give the usage message
41
\fB-o, --logfile=\fIFILE\fB\fR
42
Output to an alternate log
43
\fIFILE\fR\&. The default is no log.
45
\fB-l, --logpriority=\fILEVEL\fB\fR
47
\fILEVEL\fR\&. The default log
48
priority is ERROR\&. Possible values are :
54
Note that this option is setting the priority of the events
55
log in the alternate log file. It do not have effect on the
56
ERROR events log on stderr.
58
\fB-n, --name=\fINAME\fB\fR
59
Use container identifier \fINAME\fR\&.
60
The container identifier format is an alphanumeric string.
63
To send the signal 26 to the process pi1 running in container
67
lxc-execute -n 123 -- pi1 -d 500000
68
lxc-kill --name=123 26
88
\fBlxc-unfreeze\fR(1),
92
Daniel Lezcano <daniel.lezcano@free.fr>