On 2008-Jul-27 17:23:46 -0400, Zaphod Beeblebrox <[EMAIL PROTECTED]> wrote: > we'd need a method of remembering what file handles were >connected to so that they could be "reopened" (in this, I envision some type >of text string... maybe a URI/URL). As a bonus, this would give us process >migration between systems, too (assuming the URI were portable between self >same systems --- which isn't horribly hard with nfs mounts and whatnot).
What you are describing here sounds more like the process checkpointing functionality that Softway (I think it was) developed sometime last century. There should be a paper on it in an AUUG Conference Proceedings somewhere. Process checkpointing is somewhat different to suspend/resume: With suspend/resume, you are saving the entire system state - which is basically a matter of dumping physical RAM to disk and being able to restore it later. You don't need to be able to isolate individual processes and there's no need to 'reopen' file handles because they will automatically re-instantiate when you restore the kernel state that included them being open. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour.
pgpyhwTa6iaix.pgp
Description: PGP signature
