> : a process, you have to snapshot all related processes and the state of
> : the kernel. It's a much better idea to have general persistency and take
> : periodic system-wide snapshots.
>
> Yup. But throw a cluster into the mix and think about saving the state
> of all those sockets. It's doable, just a pain in the butt.
I am dreaming of doing an "atomic" cp /proc/pid/<> newhost:/proc/ *g*
Seriously: Shouldn't be all information relating to a process and it's
resource reside in /proc? This might be the first step to get process
migration going, since then you could implement a clean interface.
(You can implement this using other tricks, but using the proc fs has a
certain "clean" and consistent appeal to me)
-- Lars Marowsky-Brée :homepage email: \ geek, BOFH, psychopath, magician, / http://teuto.net/~lmb/ lmb@teuto.net \ killer, looney, genius, pervert / pgp-key-id: 0x09e360c5 / ff 2a 82 e8 6b 85 79 23 9c da b5 81 d4 fc 29 e6- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu