Re: How to get XQuartz 2.7.5 to listen on port 6000?
Re: How to get XQuartz 2.7.5 to listen on port 6000?
- Subject: Re: How to get XQuartz 2.7.5 to listen on port 6000?
- From: Per-Arne Lindqvist <email@hidden>
- Date: Mon, 03 Mar 2014 01:38:02 +0100
Running XQuartz 2.7.5 on Mac OS X 10.8.5
I have trouble getting the X11 server to respond to a client request.
XQuartz is running with an xterm application where I have set xhost +,
I have checked the box "Allow connections from network clients". In the
System Preferences, Security & Privacy, Firewall, Firewall options, I
have chosen Allow incoming connections for XQuartz (I have even tried
switching off the Firewall).
Did you restart X11 afterward? It's too late to establish a listen
socket if it's already running.
You can use `lsof -i :6000` to see if it's working.
That said, I don't know if anyone's actually tested it since using ssh
X11 forwarding is very strongly preferred to letting XQuartz listen on
the network directly.
Thanks for the tip on lsof which I didn't think of.
"lsof |grep X11" found the port, which had number 6018, it could be
seen with "netstat -an" also when I knew what to look for.
It turns out that each time X11 is restarted, the display increases by
1. It can also be found by "ps -x|grep Xquartz", where the corresponding
display number was :18.
I just found a ticket #834 at MacOS forge
(xquartz.macosforge.org/trac/ticket/834) which is exactly this issue.
Apparently Xquartz does not clean up properly on exit, but leaves locks
in /tmp/.X* They promise to fix the bug for version 2.7.6...
Rebooting resets the counter, since /tmp is flushed; it also works to
manually delete /tmp/.X*
I am aware of the security issues with xhost + etc, but I am running
the client on an old machine which does not handle ssh X forwarding.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden