I just rebooted my system and I can see that DISPLAY is set to /tmp/launch-xxxxx/:0 even though I have not started X11 yet. Clearly it must be launchd during the bootup (and not the X11 server) that sets the DISPLAY. I think it all makes sense now.
Is the socket created during the computer bootup or is it when the application call (like xterm) is issued?
Let me try to answer myself. I guess the socket must be created during the the bootup, which could explain much of my confusion. I thought that that the xterm call gets somehow intercepted by the system and which then via launchd starts the X11 server and creates the socket. But I guess it is actually the creation of the socket during the system boot that enables the launch. Is this correct?
On Dec 17, 2007 11:08 AM, Robert T Wyatt <email@hidden> wrote:
John Koren wrote: > I have one question. How is it that a plain 'xterm' call prompts launchd > to start X11 while xterm with DISPLAY set to :0 does not?
Ooh, I think I know the answer to this one! I believe it's because
launchd only understands the /tmp/launchd-xxxxx/:0 socket.
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden