.\" 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-CHECKPOINT" "1" "Mon Dec 16 11:31:06 UTC 2013" "IBM" ""

.SH NAME
lxc-checkpoint \- checkpoint a running container (not implemented yet)
.SH SYNOPSIS

\fBlxc-checkpoint
--statefile=\fIFILE\fB
--statefd=\fIFD\fB
--name=\fINAME\fB \fR [ \fB-k|-p\fR ]

.SH "DESCRIPTION"
.PP
\fBlxc-checkpoint\fR is a command
to checkpoint the specified container
\fINAME\fR and dumps its state into the file
\fIFILE\fR\&. If the
option \fB--kill\fR is specified, the application
running in the container will terminate after the checkpoint
just before resuming its execution. If the
option \fB--pause\fR is specified, the application
will be stopped after the checkpoint just before resuming
execution. The command \fBlxc-unfreeze\fR will
resume its execution.
.SH "CHECKPOINT OPTIONS"
.TP
\fB-S, --statefile=\fIFILE\fB\fR
write 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
write the state of the container in this
\fIFD\fR file descriptor.
This option is exclusive with above \fB--statefile\fR\&.
.TP
\fB-k,--kill\fR
Kill container processes after checkpoint. the processes are sent
a SIGKILL signal.

This option is mutually exclusive with the following
\fB--pause\fR option.
.TP
\fB-p,--pause\fR
Pause container processes after checkpoint. The container
will be stopped until you resume it. This option is
mutually exclusive with previously mentionned
\fB--kill\fR option.
.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 -S /share/123/chkpt1 -k
    
.fi
.PP
to checkpoint the same container and \fBpause\fR it

.nf
      lxc-checkpoint -n 123 -S /share/123/chkpt1 -p
      lxc-checkpoint --name=123 -S /share/123/chkpt1 -p
    
.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>