.\" This manpage has been automatically generated by docbook2man 
.\" from a DocBook document.  This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
.\" Please send any bug reports, improvements, comments, patches, 
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "LXC-RESTART" "1" "Mon Dec 16 11:31:06 UTC 2013" "IBM" ""

.SH NAME
lxc-restart \- restart a container from a file (not implemented yet)
.SH SYNOPSIS

\fBlxc-restart [-f
config_file][-s KEY=VAL]
--statefile=\fIFILE\fB
--statefd=\fIFD\fB\fR \fB--name=\fINAME\fB\fR

.SH "DESCRIPTION"
.PP
\fBlxc-restart\fR is a command
to restart an application from the state read in the specified
\fIFILE\fR, in a container with the
identifier \fINAME\fR\&.
If the option \fB--pause\fR
is specified, the application will be stopped after the
restart just before resuming execution. The command
\fBlxc-unfreeze\fR will be needed to resume its
execution.
.SH "RESTART OPTIONS"
.TP
\fB-S, --statefile=\fIFILE\fB\fR
read the state of the container in this
\fIFILE\fR\&.
This option is exclusive with \fB--statefd\fR below.
.TP
\fB-d, --statefd=\fIFD\fB\fR
read the state of the container in this
\fIFD\fR file descriptor.
This option is exclusive with above \fB--statefile\fR\&.
.TP
\fB-p\fR
Pause container processes after restart. The container will be
stopped until you resume it with the lxc-unfreeze command.
.TP
\fB-f, --rcfile=\fIconfig_file\fB\fR
Specify the configuration file to configure the
virtualization and isolation functionalities for the
container. This parameter should be specified if it was
specified for the \fBlxc-execute\fR
or \fBlxc-start\fR commands or if the
container configuration has to be changed at restart. The
latter may fail if the needed resources are not available
for the restart. If the container was created and
configured with \fBlxc-create\fR, this option
is not needed, the configuration will be automatically
found.
.TP
\fB   -s \fIKEY=VAL\fB \fR
Assign value \fIVAL\fR to configuration
variable \fIKEY\fR\&. This overrides any
assignment done in \fIconfig_file\fR\&.
.SH "COMMON OPTIONS"
.PP
These options are common to most of lxc commands.
.TP
\fB-?, -h, --help\fR
Print a longer usage message than normal.
.TP
\fB--usage\fR
Give the usage message
.TP
\fB-q, --quiet\fR
mute on
.TP
\fB-o, --logfile=\fIFILE\fB\fR
Output to an alternate log
\fIFILE\fR\&. The default is no log.
.TP
\fB-l, --logpriority=\fILEVEL\fB\fR
Set log priority to
\fILEVEL\fR\&. The default log
priority is ERROR\&. Possible values are :
FATAL, CRIT,
WARN, ERROR,
NOTICE, INFO,
DEBUG\&.

Note that this option is setting the priority of the events
log in the alternate log file. It do not have effect on the
ERROR events log on stderr.
.TP
\fB-n, --name=\fINAME\fB\fR
Use container identifier \fINAME\fR\&.
The container identifier format is an alphanumeric string.
.SH "EXAMPLES"
.PP
To start a new container 123 computing decimals of pi

.nf
      lxc-execute -n 123 -- pi1 -d 500000
      lxc-execute --name=123 -- pi1 -d 500000
    
.fi
.PP
to checkpoint the same container in \fBdump-death\fR
mode

.nf
      lxc-checkpoint -n 123 -S /share/123/chkpt1 -k
      lxc-checkpoint --name=123 --statefile=/share/123/chkpt1 -k
    
.fi
.PP
and to restart the same container with a different id

.nf
      lxc-restart -n 200 -S /share/123/chkpt1
      lxc-restart --name=200 --statefile=/share/123/chkpt1
    
.fi
.SH "NOTES"
.PP
Actually, this command does not operate. Its description
helps to define a CLI api for future Checkpoint / Restart
solution
.SH "SEE ALSO"
.PP
\fBlxc\fR(1),
\fBlxc-create\fR(1),
\fBlxc-destroy\fR(1),
\fBlxc-start\fR(1),
\fBlxc-stop\fR(1),
\fBlxc-execute\fR(1),
\fBlxc-kill\fR(1),
\fBlxc-console\fR(1),
\fBlxc-monitor\fR(1),
\fBlxc-wait\fR(1),
\fBlxc-cgroup\fR(1),
\fBlxc-ls\fR(1),
\fBlxc-ps\fR(1),
\fBlxc-info\fR(1),
\fBlxc-freeze\fR(1),
\fBlxc-unfreeze\fR(1),
\fBlxc-attach\fR(1),
\fBlxc.conf\fR(5)
.SH "AUTHOR"
.PP
Daniel Lezcano <daniel.lezcano@free.fr>