2,257
edits
Changes
mLine 1:
Line 1: − + − + + + + + + + + + + + + + + + + + + − = 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].+
no edit summary
[[Category:Under the hood]]
== Introduction ==
[[Category:Empty articles]]
Before we can start checkpointing processes, we have to make sure that they will not change their state. The latter not only includes opening new files, sockets, changing session and other, but also producing new children processes which, in turn, can escape from dumping procedure. In other words, the process tree itself and processes in it must be "immobilized" while we are dumping it. While sounds trivial in theory, it is problematic in real life. The checkpoint is 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 the stop signal, but doing so would disturb the process state.
So there are two ways to transparently stop the process tree:
* Capturing them with ptrace
* Freezing them using [https://www.kernel.org/doc/Documentation/cgroup-v1/freezer-subsystem.txt freezer cgroup].
== Capturing with ptrace ==
== Using freezer cgroup ==
== See also ==
* [[Tree after restore]]
* [[Checkpoint/Restore]]
== External links ==
* https://www.kernel.org/doc/Documentation/cgroup-v1/freezer-subsystem.txt
[[Category:Under the hood]]