<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Sep 2, 2014 at 2:35 AM, Cyrill Gorcunov <span dir="ltr"><<a href="mailto:gorcunov@gmail.com" target="_blank">gorcunov@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">OK, so you're basically do rather a widespread testing of criu (which<br>
is great I believe please share results on <a href="http://criu.org/What_software_is_supported" target="_blank">http://criu.org/What_software_is_supported</a>)<br>
Now back to the main problem -- I fear there is no single answer, every<br>
application you're c/r'ing need to be reviewed separately. That said<br>
-j option to inherit tty (as Pavel said) is to be deterministic<br>
and passed only when you know that you'll need to reuse tty. The<br>
patch I sent seems to be rather a hack than valid solution. Thus<br>
I propose you to update your script and create a list of applications<br>
which do not need -j option at all so that you'll have two lists:<br>
one to call criu with -j and second to call criu without it. At<br>
least that's my vision. Pavel what do you think?<br>
</blockquote></div><br></div><div class="gmail_extra">Thanks,<br><br>I will keep this in mind while working with the different workloads and will definitely let you guys know which software is being supported by criu.<br>
<br></div><div class="gmail_extra">-----<br></div><div class="gmail_extra">Sanidhya<br></div></div>