mirror of
https://github.com/checkpoint-restore/criu.git
synced 2026-07-28 04:33:49 +00:00
No description
blcrcheckpointcontainercontainerscriudmtcphighly-availablelinuxmemory-trackingmigrationparasitepost-copyrestoresnapshotsuspenduserfaultfdzero-downtime
60738eaa78
Remove getting opts from descriptors out from scm engine, this stuff is pure criu thing, so make it collect the data. The tricky change here is that parasite code needs memory to keep fd_opts on. The memory is taken from parasite args region, which is now bigger than it used to be. But that's not a big deal, as previously this space was allocated on the parasite stack (!, but with smaller chunks). On the other hand, now we have one memcpy less, as opts are put directly into the destination buffer. travis-ci: success for files: Rework send/recv-fds to be more generic Signed-off-by: Pavel Emelyanov <xemul@virtuozzo.com> |
||
|---|---|---|
| contrib | ||
| coredump | ||
| crit | ||
| criu | ||
| Documentation | ||
| images | ||
| include/common | ||
| lib | ||
| scripts | ||
| test | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| COPYING | ||
| CREDITS | ||
| INSTALL.md | ||
| Makefile | ||
| Makefile.config | ||
| Makefile.install | ||
| Makefile.versions | ||
| README.md | ||
CRIU (Checkpoint and Restore in Userspace)
An utility to checkpoint/restore tasks. Using this tool, you can freeze a running application (or part of it) and checkpoint it to a hard drive as a collection of files. You can then use the files to restore and run the application from the point it was frozen at. The distinctive feature of the CRIU project is that it is mainly implemented in user space.
The project home is at http://criu.org.
Pages worth starting with are:
- Kernel configuration, compilation, etc
- A simple example of usage
- More sophisticated example with graphical app
A video tour on basic CRIU features
How to contribute
- How to submit patches;
- Send all bug reports to mailing list;
- Spread the word about CRIU in social networks;