2.1.1 and xterm
2.1.1 and xterm
- Subject: 2.1.1 and xterm
- From: "John Koren" <email@hidden>
- Date: Sun, 16 Dec 2007 12:34:57 -0800
Thanks Ben for all the details related to launchd and the role of
/tmp/.X11-unix/X0. It is much clearer now.
I also asked earlier if launchd could ignore the display variable when the trigger application has it set to :0 (or equivalent) so that it would not launch the "spurious" xterm. Perhaps it is a bad idea but it would avoid the situations where people are searching for an extra "xterm" in their own scripts when in fact it is only a byproduct of the DISPLAY being set to :0.
-John
>Yeah, this aspect is something I'd been meaning to raise. The way that launchd is used to assign a unique socket means that no matter how many users are flipping between sessions using Fast User Switching, any of them can fire up X applications, and it will Just Work, connecting to (and starting, if necessary) an X server associated with their own private display. Using a fixed-location socket like :0 would mean that the second user who fired up an X app would wonder where the user interface went, since it would be displaying in the first user's session (or, depending on permissions, would simply fail).
-Jim
>On Dec 16, 2007, at 07:43, Ben Byer wrote:
If you are hard-coding the value 'DISPLAY=:0' on any multi-user system, you are already committing a gross hack by making two bad assumptions:
1) that the X server is already running (this is a reasonable assumption on other platforms, because often you start programs from within X11. In that case, why do you need to set DISPLAY at all?)
2) that you are the only person running X on your machine, and that someone else will not be using DISPLAY :0.
--
Ben Byer
CoreOS / BSD Technology Group, XDarwin maintainer
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden