I remotely access to my OPENsuse 11. I am using TightVNC program. There is nothing wrong with accessing. But I have to start an analysis program, an this analysis takes about 4 to 6 hours. Therefore, I want to disconnect and let my analysis continue.
But after disconnecting from suse, the program i started stops to work. Does anybody know how not to kill the program while i am not connected?
I do this sort of thing often, but unfortunately I run vnc/tightvnc from a terminal, and not being a GUI method many users hate that sort of method and dislike the way I do this.
But for the record, the way I do this is as follows. In my example I type the following two commands, on separate terminals on my PC in Germany, to remotely access my mother’s PC in North America. And I can connect, disconnect, and reconnect many times.
Thank you so much, but as you said I use GUI method and this doesn’t solve my problem i guess. As far as I know there must be a command to write the command line after my program’s name not to kill it which is working at my remote computer. By the way I use TightVNC at Vista.
c) You can start a VNC session using the ‘root’ X-window, so you could go home and run VNC on your home machine and connect to the existing root X-window. Google for this - you need to add an extra module to your /etc/X11/xorg.conf setup
> b) Install NX server - I use this all the time. You can be working on
> something, close your NX client session, go home and in the evening open
> up the session on another PC and you get the same session, just as when
> you left it.
> ‘NoMachine NX - Desktop Virtualization and Remote Access Management
> Software’ (http://www.nomachine.com/)
> … snip …
> But NX will be the best thing for your here.
Just to add a third vote for NX:
This is really the recommodation I think is the way to go. I Use it for
years in both flavours (the proprietary nomachine server and the freenx
server) at home and in the company.
It is especially optimized on using also slow network connections.
Go for it.