VNC - Revision history

Radostin: /* Video Demo */

2019-04-08T02:28:15Z

Video Demo

Radostin: Add videos

2019-04-08T02:27:08Z

Add videos

Radostin: /* Launch VNC client */

2019-04-07T23:29:47Z

Launch VNC client

Radostin: /* Start VNC server and application */

2019-04-07T23:29:30Z

Start VNC server and application

Xemul: /* Restore VNC server */

2016-10-19T06:27:25Z

Restore VNC server

Kir: /* Launch VNC client */ example for vncviewer

2015-10-29T00:09:53Z

Launch VNC client: example for vncviewer

Kir: add chmod a+x for shell script

2015-10-29T00:06:32Z

add chmod a+x for shell script

Kir: rm -i option from Xvnc (it is no longer supported (https://github.com/TigerVNC/tigervnc/pull/229) and is not needed as default is to listen to all interfaces)

2015-10-29T00:05:46Z

rm -i option from Xvnc (it is no longer supported (https://github.com/TigerVNC/tigervnc/pull/229) and is not needed as default is to listen to all interfaces)

Xemul: /* Restore VNC server */

2013-12-05T07:14:57Z

Restore VNC server

Xemul: /* Dump VNC and others */

2013-12-05T07:14:48Z

Dump VNC and others

@@ Line 76: / Line 76: @@
   Restore finished successfully. Resuming tasks.
-== Video Demos ==
+== Video Demo ==
 [https://www.youtube.com/watch?v=j4wlYY7lTDw Dumping video player with CRIU]

← Older revision		Revision as of 02:27, 8 April 2019
Line 75:		Line 75:

	Restore finished successfully. Resuming tasks.		Restore finished successfully. Resuming tasks.
		+
		+	== Video Demos ==
		+
		+	[https://www.youtube.com/watch?v=j4wlYY7lTDw Dumping video player with CRIU]
		+
		+	[https://www.youtube.com/watch?v=roJ91Kqeq5w Example how CRIU can dump and restore a TCP connections]
		+
		+	[https://www.youtube.com/watch?v=kjhuzSl6JYc Checkpoint and restore of Firefox with CRIU]

	== See also ==		== See also ==

@@ Line 45: / Line 45: @@
 After this you can start your favorite VNC client (viewer) to see what's inside the server. The latter would be visible on port 5925 (:25 argument). For example:
-  $ vncviewer localhost 25
+  $ vncviewer localhost:25
 [[File:Vnc.jpg|400px]]

@@ Line 6: / Line 6: @@
 * First, X software uses SystemV IPC shared memory to exchange data between server and application, thus you'll have to run the whole stuff in IPC namespace;
-* Second, in order to be restored reliably, it's recommended to run VNC server, window manager and application in a PID namespace;
+* Second, in order to be restored reliably, it's recommended to run [https://tigervnc.org/ VNC server], window manager and application in a PID namespace;
 * Third, when started from shell they will inherit session ID and terminal from that shell, which might block dump.
@@ Line 22: / Line 22: @@
 #!/bin/bash
 set -m
-Xvnc :25 -v -geometry 800x600 -i 0.0.0.0 -SecurityTypes none &
+Xvnc :25 -v -geometry 800x600 -interface 0.0.0.0 -SecurityTypes none &
 pid=$!
 trap "kill $pid; wait" EXIT

← Older revision		Revision as of 06:27, 19 October 2016
Line 75:		Line 75:

	Restore finished successfully. Resuming tasks.		Restore finished successfully. Resuming tasks.
		+
		+	== See also ==
		+
		+	* [[Screen]]
		+	* [[TCP connection]]

	[[Category: HOWTO]]		[[Category: HOWTO]]

← Older revision		Revision as of 00:06, 29 October 2015
Line 31:		Line 31:
	with the above "software" the server can be launched like this:		with the above "software" the server can be launched like this:

		+	# chmod a+x vnc_server.sh
	# ./newns ./vnc_server.sh icewm		# ./newns ./vnc_server.sh icewm

@@ Line 36: / Line 36: @@
 <pre>
 ?        Ss     0:00 /bin/bash ./vnc-server.sh icewm
-?        Sl     0:00  \_ Xvnc :25 -v -geometry 800x600 -i 0.0.0.0 -SecurityTypes none
+?        Sl     0:00  \_ Xvnc :25 -v -geometry 800x600 -SecurityTypes none
 ?        R      0:00  \_ icewm
 </pre>

@@ Line 65: / Line 65: @@
 == Restore VNC server ==
-  # criu restore --images-dir imgs/ --log-file rst.log -v 4 --tcp-established -d
+  # criu restore --images-dir imgs/ --log-file rst.log -v4 --tcp-established -d
 What has changed from the dump command is the action (it's restore now), the log file name (not to mix things up) and the new <code>-d</code> option. It says, that after restoring criu should exit and make the restored tree of tasks to be reparented to the init task.

@@ Line 52: / Line 52: @@
 Then you should create a directory for image files (e.g. <code>imgs</code>) and dump the tree starting from the VNC launching script
-  # criu dump -t 17854 --images-dir imgs/ --log-file dump.log -v 4 --tcp-established
+  # criu dump -t 17854 --images-dir imgs/ --log-file dump.log -v4 --tcp-established
-The <code>-v 4</code> option is required to make criu more verbose and the <code>--tcp-established</code> one is needed, to make criu handle active TCP connection -- the one between VNC server and VNC client.
+The <code>-v4</code> option is required to make criu more verbose and the <code>--tcp-established</code> one is needed, to make criu handle active TCP connection -- the one between VNC server and VNC client.
 Check the criu return code to be 0, or the imgs/dump.log file last message to be