> This has been demonstrated to be not true. Again, see ckpt for a simple
> example.
>
> Oh, right, well willingness to run inside of a container *is* something we
> would require :) Not needed for checkpointing a single process,
> however - see ckpt.
Be careful not to assume that some set of requirements on our result
is an appropriate set because, for each requirement, someone else has
demonstrated a solution that meets that requirement.
Sometimes there are tradeoffs. For example, ckpt will checkpoint/restart
a single task without kernel support, but doesn't preserve (from its README
at http://www.cs.wisc.edu/~zandy/ckpt/README):
- File descriptors of open files, special devices,
pipes, and sockets;
- Interprocess communication state (such as shared memory, semaphores,
mutex, messages);
- Kernel-level thread state;
- Process identifiers, including process id, process group;
id, user id, or group id.
and doesn't work with static bound programs (uses PRELOAD).
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[email protected]> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
