<p>Thx for the tips :)</p>
<div class="gmail_quote">5 lut 2013 18:12, <<a href="mailto:Valdis.Kletnieks@vt.edu">Valdis.Kletnieks@vt.edu</a>> napisał(a):<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Tue, 05 Feb 2013 14:07:37 +0100, Grzegorz Dwornicki said:<br>
<br>
> I guess that there may be a better API that why this thread was created in<br>
> first place. My project goal is to make process checkpoints like cryopid<br>
> had. This is for my thesis and will be GPL for everyone after my<br>
> graduaction. I am researching this subject at this point.<br>
<br>
In that case, you want to go look at the checkpoint/restart patches that are<br>
already in the kernel, and in process. Hint - it's a *lot* harder to do this<br>
right than a thesis project (unless you want to only do a very restricted<br>
subset, like "no open files", "no TCP connections", etc). In fact, a lot of<br>
the 'namespace' stuff was added to help support C/R. For instance, the PID<br>
namespace is there to deal with the fact that if you checkpoint a process with<br>
PID 23974, you need to be able to guarantee that it gets 23974 on restart (as<br>
otherwise you hit problems with getpid() and kill() not referring to the<br>
process you though it did). Of course, this majorly sucks if that PID is<br>
already in use. The solution there is to spawn a new, empty PID namespace to<br>
guarantee that number is available...<br>
<br>
<a href="https://ckpt.wiki.kernel.org/index.php/Main_Page" target="_blank">https://ckpt.wiki.kernel.org/index.php/Main_Page</a> is a good place to start.<br>
<br>
</blockquote></div>