On 3/3/2013 3:57 PM, Jon Elson wrote: > A very quick way to find out if the X server is able to display a window > from a client (the client/server terminology is backwards from the usual > meaning) is to run xclock. You can start and stop this in less than a > second > to see if the clock shows up on your screen. When you get that working, > then you can try more complex applications like LinuxCNC/Axis. > Sometimes you still need to run xhost +<remote machine address>
Xclock, or xeyes, or pretty much anything in the x11-apps package would do. I was trying to stick to an app already known to LinuxCNC users. An advantage to using glxgears is that it also tests whether the X-server supports glx at all (don't know about Mac X-servers but the early PC/Windows X-servers did not). In any case,we agree that one can test the X communications issues before moving on to LinuxCNC issues. As for xhost, that is an evil program. It should have been banished long ago. The whole point of X-tunneling through ssh is to avoid the gigantic security holes punched through systems by hacks like xhost. Regards, Kent ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
