[CRIU] Dump Process
Thouraya TH
thouraya87 at gmail.com
Wed Jul 16 06:50:06 PDT 2014
You use 3 terms interchangeably -- interrupt, stop and kill the process.
--Yes
i want just stay running the ./test.sh script
root at thouraya-Lenovo-3000-N500:/home/thouraya# criu dump -vvvv -o dump.log
*-R* -t 4172 --shell-job && echo OK
OK
it works :)
Please, i have two other questions which are importants for me:
1) i'd like to restart process on a new machine
Here is restore files in my current machine:
root at thouraya-Lenovo-3000-N500:/home/thouraya/imgDir# criu restore -d -vvv
-o restore.log && echo OK
OK
root at thouraya-Lenovo-3000-N500:/home/thouraya/imgDir# ls
cgroup.img fifo-data.img netlinksk.img sigacts-20099.img
core-19654.img fifo.img ns-files.img signalfd.img
core-20099.img filelocks-19654.img packetsk.img
signal-p-19654.img
creds-19654.img filelocks-20099.img pagemap-19654.img
signal-p-20099.img
creds-20099.img fs-19654.img pagemap-20099.img
signal-s-19654.img
dump.log fs-20099.img pages-1.img
signal-s-20099.img
eventfd.img ids-19654.img pages-2.img sk-queues.img
eventpoll.img ids-20099.img pipes-data.img stats-dump
eventpoll-tfd.img inetsk.img pipes.img stats-restore
ext-files.img inotify.img pstree.img tty.img
fanotify.img inotify-wd.img reg-files.img tty-info.img
fanotify-mark.img inventory.img remap-fpath.img tunfile.img
fdinfo-2.img mm-19654.img restore.log unixsk.img
fdinfo-3.img mm-20099.img sigacts-19654.img
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 ?
i cant't test this now because i haven't another machine with criu ..
2) i have to test criu dumping process with an application ( a binary file
which uses some input files)
i have tested this with blcr, when i restart the process on a new machine,
i have to migrate input fileson the machine
is it the same with criu ?
Thanks a lot for help and answers.
Bests.
2014-07-16 13:47 GMT+01:00 Pavel Emelyanov <xemul at parallels.com>:
> On 07/16/2014 04:32 PM, Thouraya TH wrote:
> > When dumping a process the latter must be stopped. Do you want it not to
> get
> > killed after dump, but continue running?
> >
> > Yes, that's it ? is that possible ?
>
> It's in the criu --help text:
>
> -R|--leave-running leave tasks in running state after checkpoint
>
> > 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)
> > *Without interrupting (stopping) or killing ./test.sh*
>
> You use 3 terms interchangeably -- interrupt, stop and kill the process.
> They are _all_ have _different_ meaning. Please, clarify what you want.
>
> > Thanks.
> > Best Regards.
> >
> >
> > 2014-07-16 13:17 GMT+01:00 Thouraya TH <thouraya87 at gmail.com <mailto:
> thouraya87 at gmail.com>>:
> >
> > When dumping a process the latter must be stopped. Do you want it
> not to get
> > killed after dump, but continue running?
> >
> > Yes, that's it ? is that possible ?
> > 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)
> >
> > Thanks.
> > Best Regards.
> >
> >
> >
> > 2014-07-16 13:00 GMT+01:00 Pavel Emelyanov <xemul at parallels.com
> <mailto:xemul at parallels.com>>:
> >
> > On 07/16/2014 03:12 PM, Thouraya TH wrote:
> > > Hello,
> > >
> > > Please, i have a question about the dump process.
> > > I have tested this tutorial: http://criu.org/Simple_loop
> (the second part)
> > > *A shell job
> > >
> > > 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. *
> > >
> > >
> > > /*criu dump" must be executed from another terminal. */
> > >
> > > My question:
> > > When i performed the dump process, i see that the running
> script $ ./test.sh stop
> > > That's it ?
> >
> > Not stopped, but killed.
> >
> > > i ask if there is a solution to proceed the dumping process in
> parallel with the execution of the script without stpping it ?
> >
> > When dumping a process the latter must be stopped. Do you want
> it not to get
> > killed after dump, but continue running?
> >
> > Thanks,
> > Pavel
> >
> >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20140716/47673e42/attachment.html>
More information about the CRIU
mailing list