+ "John Koren" <email@hidden>:
> I understand that when DISPLAY is set to /tmp/launch-xxxx/:0 then
> X11 windows are channeled through this socket. But what is the
> benefit of doing it that way? What was wrong with the 'localhost'?
If the X server listens on localhost, then in order to be secure
against local users, you need at the very least to set and maintain a
cookie, which requires a slightly more complicated startup sequence
for the X server: You need also to run xauth to get the cookie stored
in the user's .Xauthority file. I am not sure how complicated that
would be; perhaps not very.
> Why can't launchd set the DISPLAY to ':0'?
Because it might have to be :1, or :2, or ... depending on what other
users are running X servers on the same machine. And it is probably
beyond the current capabilities of launchd to deal with that extra
> As I mentioned earlier going through localhost still seems to
> work. If you go to terminal.app or xterm and set DISPLAY to ':0' or
> 'localhost:0' or 'your_computer_name:0' and try to launch an X
> application it will open correctly on your local screen.
It doesn't for me: The X server runs with flags -nolisten tcp.
If I run netstat -finet that confirms nothing is listening on port
6000. There must be something unusual with your setup.
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden