Re: Xquartz on 10.6.8 Server (problem)
Re: Xquartz on 10.6.8 Server (problem)
- Subject: Re: Xquartz on 10.6.8 Server (problem)
- From: JF Mezei <email@hidden>
- Date: Mon, 13 Apr 2015 15:09:35 -0400
On 15-04-06 19:06, Jeremy Huddleston Sequoia wrote:
>> -When I login at command line, who sets the DISPLAY environment
>> variable to "/tmp/launch-rvfrHh/org.macosforge.xquartz:0" ?
>
> launchd.
But launchd is only invoked when I login and it runs the LaunchAgent
org.macosforge.xquartz.startx.plist , correct ?
The plist would hacve launchd do:
> /opt/X11/lib/X11/xinit/launchd_startx /opt/X11/bin/startx -- /opt/X11/bin/Xquartz
There is no man page for launchd_startx. Does launchd_startx simply
setup the /tmp file (which appears to be empty, is that normal?) and
then arrange for DISPLAY environment variable to be set to point to it ?
Or is there much more work done when I login ?
When I start the XQuartz.app manually, does it do the same "stub" job as
calling xterm with DISPLAY pointing to that /tmp file , which triggers
the background work to get done ? Or does it actually start the X
server and also sends messages to get xinit to start ?
>launchd spawns startx which execs xinit which forks and execs /opt/X11/bin/Xquartz and xinitrc. xinitrc execs quartz-wm, and Xquartz checks in launchd to get the socket's fd.
Thanks. I will have to go through the man pages, and maybe try to start
those manually with any logging options they may have.
As an aside:
the printing add-on "foomatic" which uses Ghostscript to generate raster
files to send to various printers (like dot matrix) expects files to be
in /usr/X11 which no longer exists, since you moved everything to
/opt/X11. Adding a soft link from /usr/X11 to /opt/X11 solved the problem.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden