Timeline for How to run a program over multiple sessions (machine off and on again)
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 13 at 7:54 | comment | added | Stephen Kitt | It’s a shame that it doesn’t work for you, perhaps the VM solution in Ángel’s answer would be a better fit. Podman and Docker’s checkpointing features both use CRIU. | |
| Jan 11 at 21:06 | comment | added | Tomas By | Except for some stuff in the beginning, strace only shows mmap and rt_sigprocmask. | |
| Jan 11 at 20:19 | comment | added | Tomas By | @AndrewHenle I did actually look at that earlier, and there is nothing I recognise. It uses (I believe) the Boehm GC, however, which is a well-known source of problems. | |
| Jan 11 at 14:38 | comment | added | Andrew Henle | @TomasBy See criu.org/What_cannot_be_checkpointed. There are things that creating a perfect copy of a process address space can't duplicate, and if the process depends on such things, crui can't work. You could run your process under strace to actually see what external resources it relies on. Maybe it uses temp files, for example. | |
| Jan 11 at 8:05 | comment | added | Tomas By | Hmm Error (criu/cr-restore.c:1480): 5289 killed by signal 11: Segmentation fault Error (criu/cr-restore.c:2447): Restoring FAILED. | |
| Jan 10 at 13:57 | history | answered | Stephen Kitt | CC BY-SA 4.0 |