Changes

948 bytes added ,  16:08, 20 September 2016
no edit summary
Line 1: Line 1: −
Describe where images are put and what workdir is.
+
When working CRIU uses two directories to keep the data in.
   −
[[Memory changes tracking]] depends on the --prev-images-dir heavily.
+
== Image directory ==
[[Category:Empty articles]]
+
 
 +
This is the one specified with the <code>-D|--images-dir $path</code> option. If not given CRIU uses current working directory. This is where all [[images]] are put.
 +
 
 +
== Prev images directory ==
 +
 
 +
When using the [[memory changes tracking]] facility it's important to tell CRIU where images from previous run are. This is done by specifying the path with the <code>--prev-images-dir</code> option.
 +
 
 +
Remember, that the path given should be ''relative to the images directory'', e.g. like this
 +
 
 +
<pre>
 +
# criu dump --images-dir ./images-1 --track-mem
 +
# criu dump --images-dir ./images-2/ --prev-images-dir ../images-1 --track-mem
 +
</pre>
 +
 
 +
Symlinks in paths of absolute paths will not work as well unfortunately.
 +
 
 +
== Working dir ==
 +
 
 +
All other files, e.g. [[logging|logs]], [[irmap]] cache, sockets for [[lazy migration|lazy server]] and other go to working dir. By default the working directory is the images directory, but it's possible to override one with the <code>-W|--work-dir $path</code> option.
 +
 
 +
[[Category:API]]