Edward Croft wrote:
How about an xhost +<machine name> on ecroft, where <machine name> is the machine that you are running the xterm on?One of my coworkers is trying to export his Xwindows desktop to another machine and is having no luck. The error he gets is similar to the one below.
xterm Xt error: Can't open display: localhost:0
We tried something different and this is the response.
201]==> setenv DISPLAY ecroft:0 [202]==> xterm _X11TransSocketINETConnect: Can't connect: errno = 111 _X11TransSocketINETConnect: Can't connect: errno = 111
How about just using ssh's built-in X-forwarding?
It's really one of the best features of ssh, as it can pretty well do away with all that horrible DISPLAY fiddling and xhost munging.
[bevan@saladin ~]> ssh odin [bevan@odin ~]> printenv DISPLAY localhost:18.0 [bevan@odin ~]> xterm & [1] 4491 <xterm appears>