Difference between revisions of "Freezing the tree"
Jump to navigation
Jump to search
(Created page with "Category:Under the hood Category:Empty articles") |
|||
| Line 1: | Line 1: | ||
[[Category:Under the hood]] | [[Category:Under the hood]] | ||
[[Category:Empty articles]] | [[Category:Empty articles]] | ||
| + | |||
| + | = Overview = | ||
| + | |||
| + | Before we can start checkpointing processes we have to be sure that they will not produce new children processes which would escaped from dumping procedure. In other words the process tree must be persistent while we are dumping it. While sounds trivial in became problematic in real life. The checkpoint it supposed to be transparent to the application we are dumping thus it must not notice any change in process state transition. Traditionally processes are stopped with stop signal. But we have a better choise - [https://www.kernel.org/doc/Documentation/cgroup-v1/freezer-subsystem.txt a freezer cgroup]. | ||
Revision as of 16:44, 19 September 2016
Overview
Before we can start checkpointing processes we have to be sure that they will not produce new children processes which would escaped from dumping procedure. In other words the process tree must be persistent while we are dumping it. While sounds trivial in became problematic in real life. The checkpoint it supposed to be transparent to the application we are dumping thus it must not notice any change in process state transition. Traditionally processes are stopped with stop signal. But we have a better choise - a freezer cgroup.