1LXC-KILL(1) LXC-KILL(1)
2
3
4
6 lxc-kill - Send a signal to the process 1 of the container.
7
9 lxc-kill --name=NAME SIGNUM
10
12 lxc-kill send the SIGNUM signal to the first process of the container.
13
14 The SIGNUM is a numeric value, the signal name is not supported.
15
16 If this command is used on an application container ran by lxc-execute,
17 the lxc-init will receive the signal and will forward it to the process
18 2 which is the command specified in the command line. See lxc-execute
19 (1). Obviously the SIGKILL and SIGSTOP signals are not able to be for‐
20 warded, (as per the signal(7) man page).
21
23 These options are common to most of lxc commands.
24
25 -?, -h, --help
26 Print a longer usage message than normal.
27
28 --usage
29 Give the usage message
30
31 -q, --quiet
32 mute on
33
34 -o, --logfile=FILE
35 Output to an alternate log FILE. The default is no log.
36
37 -l, --logpriority=LEVEL
38 Set log priority to LEVEL. The default log priority is ERROR.
39 Possible values are : FATAL, CRIT, WARN, ERROR, NOTICE, INFO,
40 DEBUG.
41
42 Note that this option is setting the priority of the events log
43 in the alternate log file. It do not have effect on the ERROR
44 events log on stderr.
45
46 -n, --name=NAME
47 Use container identifier NAME. The container identifier format
48 is an alphanumeric string.
49
51 To send the signal 26 to the process pi1 running in container 123 :
52
53 lxc-execute -n 123 -- pi1 -d 500000
54 lxc-kill --name=123 26
55
56
57
59 lxc(1), lxc-create(1), lxc-destroy(1), lxc-start(1), lxc-stop(1), lxc-
60 execute(1), lxc-kill(1), lxc-console(1), lxc-monitor(1), lxc-wait(1),
61 lxc-cgroup(1), lxc-ls(1), lxc-ps(1), lxc-info(1), lxc-freeze(1), lxc-
62 unfreeze(1), lxc.conf(5)
63
65 Daniel Lezcano <daniel.lezcano@free.fr>
66
67
68
69IBM Mon Jul 26 17:09:32 UTC 2010 LXC-KILL(1)