Geek Answers Handbook

Attach / Detach Remote Eclipse Instance

When using Eclipse on top of X-Windows on a remote shell (X-port forwarding), is there a way to just disconnect my X-connection and return to the process later. For a bit more clarity, I am on a Windows machine and should reboot. I would like Eclipse to work and return to where I left off. Eclipse runs on my Windows machine through an X-Server connected to a Linux server.

I think something like tmux could do the trick. However, I am doing Ctrl-Z to stop Eclipse, and it does not close the Eclipse window. If I restart X-Server on Windows, Eclipse fails when I try fg 1 . Any other options?

+7
eclipse linux
source share
3 answers

I have no experience with him, but xpra sounds exactly the way you are looking.

+3
source share

Xpra did everything I needed, but it was unclear how this worked. I was able to get it to work by opening two PuTTY sessions in windows, one server and one client. In addition, the Google code is out of date. Instead, install from http://xpra.devloop.org.uk/dists/xpra-0.0.7.9.tar.bz2 . I'm not sure how this is any different, but it worked for me. README tells how to create a package. You need to be able to - get a bunch of other things. But here are the missing parts on how to make it work, as I described above:

Installation server:

 cd ~ / download / xpra / xpra-0.0.7.9
 export PYTHONPATH = $ PWD / install / lib / python: $ PYTHONPATH
 ./install/bin/xpra start: 10
 export DISPLAY =: 10
 xterm &

Installation Client:

 cd ~ / download / xpra / xpra-0.0.7.9
 export PYTHONPATH = $ PWD / install / lib / python: $ PYTHONPATH
 ./install/bin/xpra attach: 10

Notes:

  • Windows xpra installer is not required for this configuration. I do not know what he should do.
  • Be sure to run Xming on Windows.
  • Be sure to enable X port forwarding in the PuTTY client window.
  • Run everything you want from the xterm window. (i.e. Eclipse)
  • You can close the server window after xterm completes.
  • Press ctrl-c in the client window to disconnect from the session.
  • Repeat all client commands to reconnect ... even after restarting PuTTY, Xming itself, or Windows itself.
+4
source share

Which protocol is best suited to your needs depends on the availability of bandwidth, latency requirements, and the type of client OS you are using. Since you are using MS Windows, Xpra, created using the GTK / win32 proprietary toolkit, should be fairly fast, NX will use the local X server (which is slower, but you will benefit from optimizing the NX network ...).

There is a more detailed comparison of these protocols that may help you choose.

The tool in the link above makes it easy to start and pause sessions from remote computers, it is a graphical interface for Xpra, NX, VNC, etc., so you do not need to remember where the sessions are located or which port they are on. If you use only one session, always on the same machine, always on the same port, this may be redundant for your needs.

+1
source share

More articles:


All Articles