| |||||||||||||
Kernel-based checkpoint and restartKernel-based checkpoint and restartPosted Aug 21, 2008 12:21 UTC (Thu) by stevelord (guest, #53493)Parent article: Kernel-based checkpoint and restart
Bit late to the game here, but here is an early implementation I did back in 1993, the running process was saved as a new executable which you could just fire up again. Yes, I had seen inside the Cray implementation, and trust me, this bears no resemblance to it, and you would run screaming for the hills if you saw it! http://ftp.metalab.unc.edu/pub/historic-linux/ftp-archive...
(Log in to post comments)
Kernel-based checkpoint and restart Posted Aug 22, 2008 20:04 UTC (Fri) by nix (subscriber, #2304) [Link] It's unexec()! Yay! (You're an Emacs user, I trust. That or a Lisp hacker. Nobody else ever treats memory images as something *executable* :) )
Kernel-based checkpoint and restart Posted Sep 17, 2008 2:08 UTC (Wed) by roelofs (guest, #2599) [Link] Nobody else ever treats memory images as something *executable* :)Wot's this, then? That's the very definition of a DOS .COM file! I wrote more than a couple of those m'self... Greg
Kernel-based checkpoint and restart Posted Sep 17, 2008 7:25 UTC (Wed) by nix (subscriber, #2304) [Link]
They're not generally produced by snapshotting a running process (the same
one that's doing the snapshotting) and dumping it out to disk. (Also, unexec() can produce things like ELF files, and as far as I recall it does it without using the OS's core-dumping mechanism.)
|
|||||||||||||