Simple loop - Revision history

Radostin: /* Dump */ Add a single line tip

2018-12-13T03:51:15Z

Dump: Add a single line tip

Xemul: the same

2014-07-15T15:14:21Z

the same

Xemul: -t is not needed on restore

2014-07-15T15:14:03Z

-t is not needed on restore

Kir: crtools -> criu

2013-04-30T17:06:07Z

crtools -> criu

Kir: reorganized, simplified, fixed english etc.

2013-04-12T23:10:39Z

reorganized, simplified, fixed english etc.

Xemul: Categorize

2013-04-12T14:32:09Z

Categorize

Xemul: /* Dumping one shell job */

2013-04-12T14:31:42Z

Dumping one shell job

Xemul: spelling

2013-04-12T14:30:55Z

spelling

Xemul: Intro

2013-04-12T14:30:27Z

Intro

Xemul: Xemul moved page Quick start guide to Simple loop without leaving a redirect: This is not quick start guide, but HOWTO describing what people usually do with CRIU when they first meet one

2013-04-12T14:27:37Z

Xemul moved page Quick start guide to Simple loop without leaving a redirect: This is not quick start guide, but HOWTO describing what people usually do with CRIU when they first meet one

@@ Line 38: / Line 38: @@
   # criu dump -t 2221 -vvv -o dump.log && echo OK
   OK
 === Check dump files ===

@@ Line 88: / Line 88: @@
 === Restore ===
-  #  criu restore -vvvv -o restore.log -t 2621 --shell-job
+  #  criu restore -vvvv -o restore.log --shell-job
   Fri Apr 12 12:41:09 MSK 2013
   Fri Apr 12 12:41:10 MSK 2013
 [[Category:HOWTO]]

@@ Line 56: / Line 56: @@
 Restore the test process:
-  # criu restore -d -t 2221 -vvv -o restore.log && echo OK
+  # criu restore -d -vvv -o restore.log && echo OK
   OK

@@ Line 18: / Line 18: @@
 === Run (isolated) ===
-Now, if you try to simply run and try to dump such a program, crtools will  fail. The reason is a program you launch from the shell shares some common resources with the shell, notably its session and terminal. Crtools has a built-in check that makes sure there are no such resources.
+Now, if you try to simply run and try to dump such a program, criu will  fail. The reason is a program you launch from the shell shares some common resources with the shell, notably its session and terminal. Criu has a built-in check that makes sure there are no such resources.
 To remove the dependency on a current terminal, let's executed our script in a new session and redirect its output to a file:
@@ Line 36: / Line 36: @@
 Dump it:
-  # crtools dump -t 2221 -vvv -o dump.log && echo OK
+  # criu dump -t 2221 -vvv -o dump.log && echo OK
   OK
@@ Line 56: / Line 56: @@
 Restore the test process:
-  # crtools restore -d -t 2221 -vvv -o restore.log && echo OK
+  # criu restore -d -t 2221 -vvv -o restore.log && echo OK
   OK
@@ Line 64: / Line 64: @@
 For that we need to execute our test script or another program (e.g. "top") from a terminal without any redirection.
-Note crtools only supports [http://en.wikipedia.org/wiki/Pseudo_terminal Unix98 PTYs].
+Note criu only supports [http://en.wikipedia.org/wiki/Pseudo_terminal Unix98 PTYs].
 === Run ===
@@ Line 75: / Line 75: @@
 === Dump ===
-Currently crtools doesn't support a stopped task, so "crtools dump" must be executed from another terminal.
+Currently criu doesn't support a stopped task, so "criu dump" must be executed from another terminal.
-  # crtools dump -t 2621
+  # criu dump -t 2621
   (00.012929) Error (tty.c:1022): tty: Found dangling tty with sid 940 pgid 2621 (pts) on peer fd 0. Consider using --shell-job option.
   (00.013111) Error (cr-dump.c:1636): Dumping FAILED.
-See, crtools asks to set the <code>--shell-job</code>, because we try to dump only a part of a session and a slave end of a tty pair. It is a common rule to ask a user, if only a part of something is dumped.
+See, criu asks to set the <code>--shell-job</code>, because we try to dump only a part of a session and a slave end of a tty pair. It is a common rule to ask a user, if only a part of something is dumped.
-  # crtools dump -vvvv -o dump.log -t 2621 --shell-job && echo OK
+  # criu dump -vvvv -o dump.log -t 2621 --shell-job && echo OK
   OK
 === Restore ===
-  $  ~/crtools/crtools restore -vvvv -o restore.log -t 2621 --shell-job
+  #  criu restore -vvvv -o restore.log -t 2621 --shell-job
   Fri Apr 12 12:41:09 MSK 2013
   Fri Apr 12 12:41:10 MSK 2013
 [[Category:HOWTO]]

@@ Line 1: / Line 1: @@
-This HOWTO describes how to dump a very simple shell scripts that just loops and shows that it's alive.
+This HOWTO describes how to dump a trivial program.
-First of all, if you try to simply launch such program and dump it crtools will  fail. This is because the program you launch from shell shared session and terminal with the shell itself, but crtools should make sure, that no resources are used by external processes. So this simple test would be a little bit trickier, that just it.
+== Simplest case ==
   $ cat > test.sh <<-EOF
   #!/bin/sh
@@ Line 12: / Line 14: @@
   done
   EOF
   $ chmod +x test.sh
   $ setsid ./test.sh  < /dev/null &> test.log &
   [2] 2220
   [2]+  Done                    setsid ./test.sh < /dev/null &>test.log
-* Get pid of the test process:
+=== Dump ===
   $  ps -C test.sh
    PID TTY          TIME CMD
 ?        00:00:00 test.sh
-* Dump the test process.
-  $  ~/crtools/crtools dump -t 2221 -vvv -o dump.log && echo OK
+Dump it:
   OK
-* The state of the processes are saved in a few files:
   $  ls
   core-2221.img   eventpoll-tfd.img  filelocks-2221.img  inotify.img       netlinksk.img     pipes.img         sigacts-2424.img   test.log
@@ Line 34: / Line 51: @@
   eventfd.img     fifo-data.img      ids-2424.img        mm-2221.img       pages-2.img       rlimit-2424.img   signal-s-2424.img  vmas-2221.img
   eventpoll.img   fifo.img           inetsk.img          mm-2424.img       pipes-data.img    sigacts-2221.img  sk-queues.img      vmas-2424.img
-* Restore the test process.
-  $ ~/crtools/crtools restore -d -t 2221 -vvv -o restore.log && echo OK
+=== Restore ===
   OK
-== Dumping one shell job ==
+== A shell job ==
-Now let's see how to dump the same program when it is just launched from shell without additional setsid-s and stdio-s redirection.
   $ ./test.sh
   $ ps -C test.sh
     PID TTY          TIME CMD
 pts/1    00:00:00 test.sh
 Currently crtools doesn't support a stopped task, so "crtools dump" must be executed from another terminal.
-  $  ~/crtools/crtools dump -t 2621
   (00.012929) Error (tty.c:1022): tty: Found dangling tty with sid 940 pgid 2621 (pts) on peer fd 0. Consider using --shell-job option.
   (00.013111) Error (cr-dump.c:1636): Dumping FAILED.
-crtools asks to set the option --shell-job, because we try to dump only a part of session and a slave point of a tty pair. It's a common rule to ask a user, if only a part of something is dumped.
-  $ ~/crtools/crtools dump -vvvv -o dump.log -t 2621 --shell-job && echo Ok
+See, crtools asks to set the <code>--shell-job</code>, because we try to dump only a part of a session and a slave end of a tty pair. It is a common rule to ask a user, if only a part of something is dumped.
-  Ok
   $  ~/crtools/crtools restore -vvvv -o restore.log -t 2621 --shell-job
   Fri Apr 12 12:41:09 MSK 2013

← Older revision		Revision as of 14:32, 12 April 2013
Line 57:		Line 57:
	Fri Apr 12 12:41:09 MSK 2013		Fri Apr 12 12:41:09 MSK 2013
	Fri Apr 12 12:41:10 MSK 2013		Fri Apr 12 12:41:10 MSK 2013
		+
		+	[[Category:HOWTO]]

@@ Line 3: / Line 3: @@
 First of all, if you try to simply launch such program and dump it crtools will  fail. This is because the program you launch from shell shared session and terminal with the shell itself, but crtools should make sure, that no resources are used by external processes. So this simple test would be a little bit trickier, that just it.
-== Dumping a simplest process in a new session without controll terminal ==
+== Dumping a simplest process in a new session without control terminal ==
-* For that we can create a shell script, which will report date and time every second. For removing dependences on a current terminal it will be executed in a new session and output will be redirected in a file.
+* For that we can create a shell script, which will report date and time every second. For removing dependencies on a current terminal it will be executed in a new session and output will be redirected in a file.
   $ cat > test.sh <<-EOF
   #!/bin/sh

← Older revision	Revision as of 14:27, 12 April 2013
(No difference)