2,257
edits
Changes
Jump to navigation
Jump to search
Line 103:
Line 103: + + + + + + + + + + + + + + + + + + + + + + + + + + + +
no edit summary
Launch a terminal, then some application. It will attach to X and you'd see it on the screen.
Launch a terminal, then some application. It will attach to X and you'd see it on the screen.
== Dump VNC and others ==
Then you should create a directory for image files (e.g. <code>imgs</code>) and dump the tree starting from the VNC launching script
<pre>
# crtools dump -t 17854 --images-dir imgs/ --log-file dump.log -v 4 --tcp-established
</pre>
The <code>-v 4</code> option is required to make crtools more verbose and the <code>--tcp-established</code> one is needed, to make crtools handle active TCP connection -- the one between VNC server and VNC client.
Check the crtools return code to be 0, or the imgs/dump.log file last message to be
<pre>
Dumping finished successfully
</pre>
After this the VNC client would see, that the server got stuck and any moving picture(s) in the screen would be frozen. Hurry up and proceed to the restore stage, as TCP timeout may occur and abort the frozen connection.
== Restore VNC server ==
<pre>
# crtools restore -t 17854 --images-dir imgs/ --log-file rst.log -v 4 --tcp-established -d
</pre>
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 crtools should exit and make the restored tree of tasks to be reparented to the init task.
Check the crtools return code to be 0, or the imgs/rst.log file last message to be
<pre>
Restore finised successfully. Resuming tasks.
</pre>