[2305] in athena10
Re: [Debathena] #206: Define behavior around zwgc and remote X11
daemon@ATHENA.MIT.EDU (Debathena Trac)
Wed Apr 15 23:36:57 2009
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@mit.edu
To: jdreed@mit.edu, xavid@mit.edu
Date: Thu, 16 Apr 2009 03:36:24 -0000
Reply-To:
Message-ID: <052.2313979c435d31804501d0c366d082d6@mit.edu>
In-Reply-To: <043.3e6b79eb35f4f0dae95a1ca12d5276d0@mit.edu>
Content-Transfer-Encoding: 8bit
#206: Define behavior around zwgc and remote X11 sessions------------------------+---------------------------------------------------
Reporter: jdreed | Owner:
Type: enhancement | Status: new
Priority: major | Component: --
Keywords: |
------------------------+---------------------------------------------------
Comment(by jdreed):
Replying to [comment:2 xavid]:
> The fact that it's totally nonobvious that some of your windowgrams are
coming from the remote server, especially if you're not actually taking
advantage of X forwarding.
I'm not sure what you mean by "not taking advantage of X forwarding". We
don't enable X11 forwarding by default right? Users should still have to
type ssh -X (or -Y) if they want X forwarding, so I'm not sure when a user
would be connecting with X forwarding without knowing it.
> I would propose that we have as default behavior not running zwgc for
SSH sessions of any type, but document this as a change in Debathena and
provide a simple way using zephyr variables to enable the old behavior.
Fair enough, we can simply invert the description above and only run zwgc
in .login/.bash_login if $DISPLAY is set and the zephyr variable
"remotex11" is true. I think if $DISPLAY is not set (ie: a tty ssh
session), we should run zwgc regardless, because it won't have any effect
anyway unless the user has set fallback=true.
-- Ticket URL: <http://debathena.mit.edu/trac/ticket/206#comment:3>Debathena <http://debathena.mit.edu/>MIT Debathena Project
