[FreeNX-kNX] unix:port for DISPLAY causes (me) problems
Scott Moser
ssmoser at us.ibm.com
Mon Mar 14 16:32:43 UTC 2005
Hey all,
Just started using freenx and nomachine. I'm very happy with it so
far.
When I first tried using it, my freenx session would simply hang. I
had no idea why. It turned out that the freenx server machine was
trying to do X traffic to a machine called 'unix'. This was a result of
the nxnode setting up the DISPLAY and exporting DISPLAY=unix:1000.0
Unfortunately for me, the X libraries must first check hostnames,
then fall back to unix sockets for the special word 'unix'.
I worked around the problem by simply taking out the 'search' line in
/etc/resolv.conf that caused the problem, but I'd still like to search
that domain for my dns lookups.
Just as a test, I tried omitting the 'unix:' from display inside a
terminal inside or outside the freenx session, and it seemed to work for
me. Is there a reason why nxnode uses 'unix:' the prefix 'unix' ?
a patch is omitted as simply search and replace for 'unix:' with ':'
in /usr/bin/nxnode.
Thanks for your work on freenx. Its great.
More information about the FreeNX-kNX
mailing list