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-RESTART" "1" "20 May 2011" "IBM" ""
9
lxc-restart \- restart a container from a file (not implemented yet)
13
config_file][-s KEY=VAL]
14
--statefile=\fIFILE\fB
15
--statefd=\fIFD\fB\fR \fB--name=\fINAME\fB\fR
19
\fBlxc-restart\fR is a command
20
to restart an application from the state read in the specified
21
\fIFILE\fR, in a container with the
22
identifier \fINAME\fR\&.
23
If the option \fB--pause\fR
24
is specified, the application will be stopped after the
25
restart just before resuming execution. The command
26
\fBlxc-unfreeze\fR will be needed to resume its
30
\fB-S, --statefile=\fIFILE\fB\fR
31
read the state of the container in this
33
This option is exclusive with \fB--statefd\fR below.
35
\fB-d, --statefd=\fIFD\fB\fR
36
read the state of the container in this
37
\fIFD\fR file descriptor.
38
This option is exclusive with above \fB--statefile\fR\&.
41
Pause container processes after restart. The container will be
42
stopped until you resume it with the lxc-unfreeze command.
44
\fB-f, --rcfile=\fIconfig_file\fB\fR
45
Specify the configuration file to configure the
46
virtualization and isolation functionalities for the
47
container. This parameter should be specified if it was
48
specified for the \fBlxc-execute\fR
49
or \fBlxc-start\fR commands or if the
50
container configuration has to be changed at restart. The
51
latter may fail if the needed resources are not available
52
for the restart. If the container was created and
53
configured with \fBlxc-create\fR, this option
54
is not needed, the configuration will be automatically
57
\fB -s \fIKEY=VAL\fB \fR
58
Assign value \fIVAL\fR to configuration
59
variable \fIKEY\fR\&. This overrides any
60
assignment done in \fIconfig_file\fR\&.
63
These options are common to most of lxc commands.
66
Print a longer usage message than normal.
69
Give the usage message
74
\fB-o, --logfile=\fIFILE\fB\fR
75
Output to an alternate log
76
\fIFILE\fR\&. The default is no log.
78
\fB-l, --logpriority=\fILEVEL\fB\fR
80
\fILEVEL\fR\&. The default log
81
priority is ERROR\&. Possible values are :
87
Note that this option is setting the priority of the events
88
log in the alternate log file. It do not have effect on the
89
ERROR events log on stderr.
91
\fB-n, --name=\fINAME\fB\fR
92
Use container identifier \fINAME\fR\&.
93
The container identifier format is an alphanumeric string.
96
To start a new container 123 computing decimals of pi
99
lxc-execute -n 123 -- pi1 -d 500000
100
lxc-execute --name=123 -- pi1 -d 500000
104
to checkpoint the same container in \fBdump-death\fR
108
lxc-checkpoint -n 123 -S /share/123/chkpt1 -k
109
lxc-checkpoint --name=123 --statefile=/share/123/chkpt1 -k
113
and to restart the same container with a different id
116
lxc-restart -n 200 -S /share/123/chkpt1
117
lxc-restart --name=200 --statefile=/share/123/chkpt1
122
Actually, this command does not operate. Its description
123
helps to define a CLI api for future Checkpoint / Restart
129
\fBlxc-destroy\fR(1),
132
\fBlxc-execute\fR(1),
134
\fBlxc-console\fR(1),
135
\fBlxc-monitor\fR(1),
142
\fBlxc-unfreeze\fR(1),
146
Daniel Lezcano <daniel.lezcano@free.fr>
added
removed
doc/lxc-restart.1
