Difference between revisions of "Ifarm graphic mode"
(→vnc (recommended)) |
|||
Line 34: | Line 34: | ||
vncviewer localhost:1 & (use other port number if not 1 in last step) | vncviewer localhost:1 & (use other port number if not 1 in last step) | ||
(now you are inside ifarm and an xterm is open for you to use) | (now you are inside ifarm and an xterm is open for you to use) | ||
− | vncserver -kill :1 ('''make sure to kill the server after you using it to free resource on ifarm, otherwise it will keep running even after you log out!''') | + | vncserver -kill :1 ('''note the space before colons, make sure to kill the server after you using it to free resource on ifarm, otherwise it will keep running even after you log out!''') |
In principle, we don't need Xwindow forwarding to use vncviewer on ifarm. We could use a local vncviewer and ssh tunneling for better performance. This can be important if you are not on jlab internal network. ask me and I can write a howto if nessary | In principle, we don't need Xwindow forwarding to use vncviewer on ifarm. We could use a local vncviewer and ssh tunneling for better performance. This can be important if you are not on jlab internal network. ask me and I can write a howto if nessary |
Revision as of 09:43, 6 May 2017
Why
Usually we are running code on ifarm without caring about graphic because it's used for a test ground for farm job anyway.
Sometimes we do want to test a code's graphic feature. For example, it's a common system we all have access and can be used for debug.
Xwindow forwarding (not recommended)
One way to do it is simply use Xwindow forwarding by ssh into ifarm and run the code. but the problem is that Xwindow graphic is always rendered in your local machine. So not only the test can have different results for different people because their local machines are different. Sometimes, it can cause crash of your local machine if your code is not nice and your local machine is very different from ifarm.
if your local machine is linux or Mac which has Xwindows ssh -XY your_lab_username@ifarm (login with Xwindow forwarding enabled) xclock & (test if Xwindow forwarding works)
If you local machine is windows, you need to enable Xwindows forwarding in putty option and have a Xwindow server like Xming-mesa running. then test if "xclock" works
vnc (recommended)
tested on ifarm1401 and ifarm1402 as of 2017/05
The better way to do it is through a vnc inside ifarm. This way the code won't crash because it runs within the same environment where it is compiled and everyone will see same result. Here is how to do it
First login into ifarm with Xwindow forwarding enabled (this is to use vncviwer) mkdir .vnc edit .vnc/xstartup with lines below #!/bin/sh xsetroot -solid grey vncconfig -iconic & xterm -geometry 160x50+10+10 -ls -title "$VNCDESKTOP Desktop" & metacity & chmod 755 .vnc/xstartup vncserver (start vnc server, give a password if running it first time, note the port number output on screen) vncviewer localhost:1 & (use other port number if not 1 in last step) (now you are inside ifarm and an xterm is open for you to use) vncserver -kill :1 (note the space before colons, make sure to kill the server after you using it to free resource on ifarm, otherwise it will keep running even after you log out!)
In principle, we don't need Xwindow forwarding to use vncviewer on ifarm. We could use a local vncviewer and ssh tunneling for better performance. This can be important if you are not on jlab internal network. ask me and I can write a howto if nessary
For any question, email Zhiwen Zhao zwzhao@jlab.org Zhiwen