Changes

Jump to: navigation, search

CGroups

43 bytes added, 19:39, 20 September 2016
CGroups restoring strategy: proper formatting
When restoring cgroups CRIU may meet already existing cgroup controllers and as result it relies on user choice how to behave in such case: should it overwrite existing properties with values from the image or should ignore them? Or maybe it is unacceptable to modify any existing cgroup?
To break a tie CRIU supports that named restore modes, which should be specified as an addition to <code>--manage-cgroups=''mode''</code> option. Mode The <code>''mode''</code> argument may be one of the following:
# * <code>none</code>. Do not restore cgroup properties but require cgroup to pre-exist at the moment of restore procedure.# * <code>props</code>. Restore cgroup properties and require cgroup to pre-exist.# * <code>soft</code>. Restore cgroup properties if only cgroup has been created by *criu*, otherwise do not restore properies.# * <code>full</code>. Always restore all cgroups and their properties.# * <code>strict</code>. Restore all cgroups and their properties from the scratch, requiring them to not present in the system.
By default , <code>soft</code> is assigned if <code>--manage-cgroups</code> option passed without an argument (i.e. the same as <code>--manage-cgroups=soft</code>).
[[Category:Under the hood]]

Navigation menu