What about using Cryopid to "snapshot" a system as a moment in time and have that used as a wake up point.
On Tuesday 18 March 2008, Oren Beck wrote:
What about using Cryopid to "snapshot" a system as a moment in time and have that used as a wake up point.
Uhhh... Cryopid was designed exactly for when you *don't* want to do that.
Software Suspend 2 is what you want to do something like that. Of course, your snapshot is only useful once, but this kind of low-level checkpointing (which is the same level as Cryopid) is always going to have that limitation.
Cryopid was what happened when I brought up per-application (eg, less than a full system) suspending on the SwSusp2 list some years ago. Pretty neat toy, but I don't think any real world use has come of it so far-- the main problem being that you lose any open I/O (other than stdio), which is generally the purpose of any application running.
On Tue, Mar 18, 2008 at 9:50 PM, Luke -Jr luke@dashjr.org wrote:
Cryopid was what happened when I brought up per-application (eg, less than a full system) suspending on the SwSusp2 list some years ago. Pretty neat toy, but I don't think any real world use has come of it so far-- the main problem being that you lose any open I/O (other than stdio), which is generally the purpose of any application running.
it seems like ptrace and so on could be used to construct a network of related files and freeze them all, along with metadata needed to reconstruct the internal plumbing
the problem seems related to file descriptor migration in a plan-9 or mosix (which has been shut down as recent way-fast CPUs and distcc have obviated it) sense
-
David Nicol -
Luke -Jr -
Oren Beck