1,067
edits
Changes
don't use PRE for one-liners, use space. Also s/finised/finished/
with the above "software" the server can be launched like this:
with the above "software" the server can be launched like this:
# ./newns ./vnc_server.sh icewm
# ./newns ./vnc_server.sh icewm
After this you will see the process tree like below:
After this you will see the process tree like below:
Then you should create a directory for image files (e.g. <code>imgs</code>) and dump the tree starting from the VNC launching script
Then you should create a directory for image files (e.g. <code>imgs</code>) and dump the tree starting from the VNC launching script
# crtools dump -t 17854 --images-dir imgs/ --log-file dump.log -v 4 --tcp-established
# crtools dump -t 17854 --images-dir imgs/ --log-file dump.log -v 4 --tcp-established
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.
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
Check the crtools return code to be 0, or the imgs/dump.log file last message to be
Dumping finished successfully
Dumping finished successfully
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.
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 ==
== Restore VNC server ==
# crtools restore -t 17854 --images-dir imgs/ --log-file rst.log -v 4 --tcp-established -d
# crtools restore -t 17854 --images-dir imgs/ --log-file rst.log -v 4 --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 crtools should exit and make the restored tree of tasks to be reparented to the init task.
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
Check the crtools return code to be 0, or the imgs/rst.log file last message to be
Restore finised successfully. Resuming tasks.
Restore finished successfully. Resuming tasks.
[[Category: HOWTO]]
[[Category: HOWTO]]