Biggest user-visible change: launchd support for X11. The only
situation where you should need to manually start X11.app is if you
are only running remote X11 applications.
The way that this is accomplished is by some slight-of-hand with the
$DISPLAY variable -- if you look, it should be something like
"/tmp/launch-vbXRyu/:0". If an X client connects to this, it will
actually connect to launchd, which will start Xquartz if needed and
pass the client's socket to the server.
All of that should be invisible to you; the X client library
(libX11.dylib) was modified to support this, and all X11 applications
link against this library. "DISPLAY=:0" would still work if X11.app
is already running, but it will not trigger X11 to launch.
Ah ha! We have an application which uses X11 and have always used a
"starter" program which starts X11 and then our own X11 app. With
Leopard betas, the way we were starting X11 stopped working and we
didn't know why. It would be really nice if this had been documented.
Is there some reason why the socket name has to be so cryptic?
What does the vbXRyu stand for (if anything).
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden