<div dir="ltr"><div><div><div>You use 3 terms interchangeably -- interrupt, stop and kill the process. --Yes<br>i want just stay running the ./test.sh script<br><br>root@thouraya-Lenovo-3000-N500:/home/thouraya# criu dump -vvvv -o dump.log <b>-R</b> -t 4172 --shell-job && echo OK<br>
OK<br></div>it works :)<br><br></div><div>Please, i have two other questions which are importants for me:<br></div><div>1) i'd like to restart process on a new machine <br>Here is restore files in my current machine:<br>
root@thouraya-Lenovo-3000-N500:/home/thouraya/imgDir# criu restore -d -vvv -o restore.log && echo OK<br>OK<br>root@thouraya-Lenovo-3000-N500:/home/thouraya/imgDir# ls<br>cgroup.img fifo-data.img netlinksk.img sigacts-20099.img<br>
core-19654.img fifo.img ns-files.img signalfd.img<br>core-20099.img filelocks-19654.img packetsk.img signal-p-19654.img<br>creds-19654.img filelocks-20099.img pagemap-19654.img signal-p-20099.img<br>
creds-20099.img fs-19654.img pagemap-20099.img signal-s-19654.img<br>dump.log fs-20099.img pages-1.img signal-s-20099.img<br>eventfd.img ids-19654.img pages-2.img sk-queues.img<br>
eventpoll.img ids-20099.img pipes-data.img stats-dump<br>eventpoll-tfd.img inetsk.img pipes.img stats-restore<br>ext-files.img inotify.img pstree.img tty.img<br>fanotify.img inotify-wd.img reg-files.img tty-info.img<br>
fanotify-mark.img inventory.img remap-fpath.img tunfile.img<br>fdinfo-2.img mm-19654.img restore.log unixsk.img<br>fdinfo-3.img mm-20099.img sigacts-19654.img<br><br></div><div>
Question: i ask what can i do to restart process on the new machine ? i have just to send imgDir to the new machine and run the command criu restore ?<br></div><div>i cant't test this now because i haven't another machine with criu .. <br>
</div><div><br></div><div>2) i have to test criu dumping process with an application ( a binary file which uses some input files)<br></div><div>i have tested this with blcr, when i restart the process on a new machine, i have to migrate input fileson the machine<br>
</div><div>is it the same with criu ? <br></div><div><br></div>Thanks a lot for help and answers. <br></div>Bests. <br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-07-16 13:47 GMT+01:00 Pavel Emelyanov <span dir="ltr"><<a href="mailto:xemul@parallels.com" target="_blank">xemul@parallels.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 07/16/2014 04:32 PM, Thouraya TH wrote:<br>
> When dumping a process the latter must be stopped. Do you want it not to get<br>
> killed after dump, but continue running?<br>
><br>
> Yes, that's it ? is that possible ?<br>
<br>
</div>It's in the criu --help text:<br>
<br>
-R|--leave-running leave tasks in running state after checkpoint<br>
<div class=""><br>
> i want have the two process running in parallel: on the first terminal the ./test.sh , in the second terminal the dumping process (each x seconds i do the dumping process)<br>
</div>> *Without interrupting (stopping) or killing ./test.sh*<br>
<br>
You use 3 terms interchangeably -- interrupt, stop and kill the process.<br>
They are _all_ have _different_ meaning. Please, clarify what you want.<br>
<br>
> Thanks.<br>
> Best Regards.<br>
><br>
><br>
> 2014-07-16 13:17 GMT+01:00 Thouraya TH <<a href="mailto:thouraya87@gmail.com">thouraya87@gmail.com</a> <mailto:<a href="mailto:thouraya87@gmail.com">thouraya87@gmail.com</a>>>:<br>
<div class="">><br>
> When dumping a process the latter must be stopped. Do you want it not to get<br>
> killed after dump, but continue running?<br>
><br>
> Yes, that's it ? is that possible ?<br>
> i want have the two process running in parallel: on the first terminal the ./test.sh , in the second terminal the dumping process (each x seconds i do the dumping process)<br>
><br>
> Thanks.<br>
> Best Regards.<br>
><br>
><br>
><br>
</div>> 2014-07-16 13:00 GMT+01:00 Pavel Emelyanov <<a href="mailto:xemul@parallels.com">xemul@parallels.com</a> <mailto:<a href="mailto:xemul@parallels.com">xemul@parallels.com</a>>>:<br>
<div class="HOEnZb"><div class="h5">><br>
> On 07/16/2014 03:12 PM, Thouraya TH wrote:<br>
> > Hello,<br>
> ><br>
> > Please, i have a question about the dump process.<br>
> > I have tested this tutorial: <a href="http://criu.org/Simple_loop" target="_blank">http://criu.org/Simple_loop</a> (the second part)<br>
> > *A shell job<br>
> ><br>
> > Now let's see how to dump the same program when it is just started from the shell without any additional setsid and stdio redirection. For that we need to execute our test script or another program (e.g. "top") from a terminal without any redirection. *<br>
> ><br>
> ><br>
> > /*criu dump" must be executed from another terminal. */<br>
> ><br>
> > My question:<br>
> > When i performed the dump process, i see that the running script $ ./test.sh stop<br>
> > That's it ?<br>
><br>
> Not stopped, but killed.<br>
><br>
> > i ask if there is a solution to proceed the dumping process in parallel with the execution of the script without stpping it ?<br>
><br>
> When dumping a process the latter must be stopped. Do you want it not to get<br>
> killed after dump, but continue running?<br>
><br>
> Thanks,<br>
> Pavel<br>
><br>
><br>
><br>
<br>
</div></div></blockquote></div><br></div>