Results 1 to 7 of 7

Thread: Tight VNC

  1. #1

    Default Tight VNC

    Hello everybody,

    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?

    Thanks in advance.

    Ali KARA

  2. #2
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    26,604
    Blog Entries
    38

    Default Re: Tight VNC

    Quote Originally Posted by karaali View Post
    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.

    Code:
    ssh -t -L 5900:localhost:5900 mother@mothers-ip-address 'x11vnc -localhost -nolookup -nopw -display :0'
    Code:
    vncviewer -encodings "tight copyrect hextile" localhost:0
    where "mothers-ip-address" is the ip address of my mother's PC, and in this example her username is "mother".

    Of course I have the appropriate 5900 and 22 ports open.

    The above is fairly secure as I "pipe" (is that the right word ?? ) the vnc connection over the encrypted ssh.

    Another way to do this is use the "nomachine" program "nx". NoMachine NX - Desktop Virtualization and Remote Access Management Software ... but that is NOT a tightvnc method and hence it does not answer your question re: the method you want to employ.

  3. #3

    Default Re: Tight VNC

    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.

  4. #4
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    26,604
    Blog Entries
    38

    Default Re: Tight VNC

    Quote Originally Posted by karaali View Post
    By the way I use TightVNC at Vista.
    thats a VERY important piece of information that likely should have been included in the original post. I would not have wasted your time in replying, if I had read that in the original post.

    Still, you could give nx serious consideration. Its SIGNIFICANTLY faster than vnc and it works with Vista to access a Linux PC.

  5. #5

    Default Re: Tight VNC

    Dear Mr. Kara,
    I work in a highly engineering focussed company, and we have users who do analysis work like this all the time.
    May I suggest that you:

    a) learn about the "screen" command screen: Windows that Follow You | Linux Magazine

    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

    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

    But NX will be the best thing for your here.

  6. #6
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,654

    Default Re: Tight VNC

    jhearns wrote:
    > 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:

    @karaali
    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.


  7. #7

    Default Re: Tight VNC

    Hello again,

    Thanks for your recommendations. I was actually looking for some sort of command as I said before. But I am going to try this program soon. Thank you very much.

    Ali Kara

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •