Changes

56 bytes added ,  13:32, 12 July 2017
no edit summary
Line 1: Line 1: −
<code>criu</code> is an utility to checkpoint/restore a process tree. This page describes how to manually build and install prerequisites and the tool itself.
+
<code>criu</code> is an utility to checkpoint/restore a process tree. This page describes how to get CRIU binary on your box.
    
== Installing from packages ==
 
== Installing from packages ==
   −
Some distributions provide ready-to-use [[packages]]. If no, or the CRIU version you want is not yet there, you will need to get CRIU sources and compile it.
+
Many distributions provide ready-to-use [[packages]]. If no, or the CRIU version you want is not yet there, you will need to get CRIU sources and compile it.
   −
== Obtaining CRIU Source ==
+
== Obtaining CRIU sources ==
    
You can download the source code as a [https://download.openvz.org/criu/ release tarball] or sync the [https://github.com/xemul/criu git repository]. If you plan to modify CRIU sources (e.g. to [[How to submit patches|contribute the code back]]) the latter way is highly recommended. The latest and greatest sources are: {{Latest release}}
 
You can download the source code as a [https://download.openvz.org/criu/ release tarball] or sync the [https://github.com/xemul/criu git repository]. If you plan to modify CRIU sources (e.g. to [[How to submit patches|contribute the code back]]) the latter way is highly recommended. The latest and greatest sources are: {{Latest release}}
   −
== Build dependencies ==
+
== Installing build dependencies ==
    
=== Compiler and C Library ===
 
=== Compiler and C Library ===
Line 34: Line 34:  
Optionally, you may [[build protobuf]] from sources.
 
Optionally, you may [[build protobuf]] from sources.
   −
=== Other deps ===
+
=== Other stuff ===
 +
 
 
* <code>pkg-config</code> to check on build library dependencies.
 
* <code>pkg-config</code> to check on build library dependencies.
 
* <code>python-ipaddr</code> is used by CRIT to pretty-print ip.
 
* <code>python-ipaddr</code> is used by CRIT to pretty-print ip.
Line 42: Line 43:  
* <code>libnet-devel libnl3-devel</code> (RPM) / <code>libnet1-dev</code> (DEB) / <code>libnl-3-dev libnet-dev</code> (Ubuntu)
 
* <code>libnet-devel libnl3-devel</code> (RPM) / <code>libnet1-dev</code> (DEB) / <code>libnl-3-dev libnet-dev</code> (Ubuntu)
   −
For APT use "--no-install-recommends" parameter is to avoid asciidoc pulling in a lot of dependencies.
+
For APT use the <code>--no-install-recommends</code> parameter is to avoid asciidoc pulling in a lot of dependencies.
 
Also read about [[ZDTM test suite]] if you will run CRIU tests, those sources need other deps.
 
Also read about [[ZDTM test suite]] if you will run CRIU tests, those sources need other deps.
   −
== Linux Kernel ==
+
== Ensuring the Linux Kernel is up-to-date ==
   −
Linux kernel v3.11 or newer is required, with some specific options set. Various CRIU features might require even newer kernel. If your distribution does not provide needed kernel, you might want to [[Linux kernel|compile one yourself]]. Criu can [[check the kernel]] features presence.
+
Linux kernel v3.11 or newer is required, with some specific config options turned on. Various advanced CRIU features might require even newer kernel. If your distribution does not provide needed kernel, you might want to [[Linux kernel|compile one yourself]]. Criu can [[check the kernel]] features presence.
   −
== Build ==
+
== Building the tool ==
    
Simply run <code>make</code> in the CRIU source directory. This is the standard way, but there are some options available.
 
Simply run <code>make</code> in the CRIU source directory. This is the standard way, but there are some options available.
Line 57: Line 58:  
# You may [[Manual build deps|specify build dependencies by hands]]
 
# You may [[Manual build deps|specify build dependencies by hands]]
   −
== Installation ==
+
== Installing ==
 +
 
 
CRIU works perfectly even when run from the sources directory (with the <code>./criu/criu</code> command), but if you want to have in standard paths run <code>make install</code>. You may need to install <code>asciidoc</code> and <code>xmlto</code> packages to make install-man work.
 
CRIU works perfectly even when run from the sources directory (with the <code>./criu/criu</code> command), but if you want to have in standard paths run <code>make install</code>. You may need to install <code>asciidoc</code> and <code>xmlto</code> packages to make install-man work.