![]() ![]() The advantage of LSF involving of this procedure is to let LSF select a lightest Linux host to run your X-Window GUI application. At your Microsoft Windows desktop, by PuTTY with X11 forwarding enabled, you do ssh and login to LSF submission host.Ģ, At LSF submission host, submit your X-Window GUI application under LSF with bsub -XF option:īsub -m -XF Īt this point The X-GUI of your X-Window GUI application will be forwarded back to your Windows Desktop. Note: The steps above make sure everything is working without LSF.ġ. (2) At the LSF execution host, your run a xterm command, then the xterm GUI will be forwarded back to your Microsoft Windows desktop as well. (1) At your Linux LSF submission host, do "ssh -Y LSF-execution-host" to enable X11 forwarding and login to any LSF execution host which you wants to run your X-Window GUI of this application. ![]() To verify this, in addition to pre-request 1 and 2 above, you also need to make sure the following: To achieve this, you can use PuTTY with X11 forwarding enabled to do ssh to your Linux LSF submission host, then at that host you run an xterm command, the xterm GUI will be forwarded back to your Microsoft Windows desktop.ģ, X11 Forwarding from any Linux LSF execution host back to your Microsoft Windows desktop is working. Such as free Xming or Hummingbird Exceed.Ģ, You can do X11 Forwarding from your Linux LSF submission host back to your Microsoft Windows desktop. At the moment I use RealVNC, but I have noticed some notable latency. 1, You have a PC X server running in your Microsoft Windows desktop. Virtualization of a Linux guest on my local Windows host using for example Virtualbox with Ubuntu, and then ssh -X to the Linux box from it (here is a thread that discusses configurations for fast ssh X tunneling) cygwin with an X server and ssh -X to the remote box.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |