I also thought Brian's fix for gdm had gone in so this wouldn't be needed,
but it would be good if Brian could confirm that.
If the DISPLAY setting is still needed, could it instead be:
DISPLAY=127.0.0.1${DISPLAY}
so that it uses the existing display setting for sessions other than :0
(like Sun Rays)?
I suppose that could still break if DISPLAY was already set to include
a hostname, and safer would be something like:
DISPLAY=`echo ${DISPLAY} | sed 's/^.*:/127.0.0.1:/'`
-alan-
Takao Fujiwara - Tokyo S/W Center wrote:
> Thanks for your reviews.
> DISPLAY is kept there to follow the reply and the URL will be added in
> the comment for the reference.
>
> Regarding to PATH, I took the old file by mistake, currently
> /usr/X11/bin is added for all sessions in 0011.env.
> I don't know why /usr/sfw/bin is added in Xinitrc.tjds. /usr/sfw/bin is
> not for TX only?
>
>
> Glenn Faden-san wrote (02/13/09 03:10 AM):
>> Alan Coopersmith wrote:
>>>> +# Copied from /usr/dt/config/Xinitrc.tjds
>>>> +# Workaround Xconnecion problem if needs be
>>>> +if [ x"$DESKTOP_SESSION" = xtgnome -o x"$DESKTOP_SESSION" = xtjds ]
>>>> ; then
>>>> + DISPLAY=127.0.0.1:0.0 + PATH=${PATH}:/usr/X11/bin:/usr/sfw/bin
>>>> +fi
>>>>
>>>
>>> I don't think the $DISPLAY setting is needed any more, since the
>>> needed changes to support :0 are in libX11 (and since that hardcodes
>>> :0.0 will break displays on Sun Rays, virtual terminals, Xvncs on
>>> additional ports, etc.).
>>>
>>> The PATH setting should be applied to all sessions, not just trusted
>>> ones, as all sessions need commands in those paths (like xscreensaver).
>>>
>>>
>> See my blog entry:
>>
>> http://blogs.sun.com/gfaden/entry/improving_x11_performance_and_security
>>
>> This workaround is required to use UNIX domain sockets with TX. The
>> workaround is required until a fix in made to gdm that removing the
>> symlink between /tmp/.X11-unix and /var/tsol/doors. I'm not sure of
>> the status of the gdm issue. It was supposed to have been fixed by
>> Brian Cameron. If this has happened already, then the DISPLAY
>> workaround (and my lofs mount workaround) should be removed.
>>
>> --Glenn
>>
>
--
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
