Hi,
> DISPLAY variable is for the terminal that displays X output. You are not
> supposed to alter it, at least forcefully. It is bound to dump a
Well, I know that. My point is if I telnet into a box and work,
there is no reason why my DISPLAY should set. And as far as I know, there
is no reason why "su" should even look at what are the contents of
$DISPLAY.
> segmentation fault. It gets assigned from X startup script(I suppose) and
Can you please explain *why* should it dump core??? I have changed
DISPLAY several times before, (for several reasons) and I have never faced
this segfault.
One more point is that if I telnet into a box, why should the
DISPLAY get set to localhost? It should not be set, as I am on a plain
tty, connected through a plain old telnet.
startx (or xinit) does set it. But that is when I am physically
sitting on a console or X terminal, which is not the case here.
If I just login at some VC, then DISPLAY is not set at all, then
*why* should it get set when I connect to the *same* machine through
telnet?
It was not a newbie question. I have been using linux, both as an
admin and a developer for about 5 years now.
Regards,
Kedar.
PS - I discovered this correlation only when I begun looking for
reasons for the huge delay. It was then that I noticed that DISPLAY is
getting set unnecessarily. AFAIK, only ssh sets display to point to its
ssh-agent for secure X11 connections over network, telnet doesn't play
around with $DISPLAY.
-----------------------------------------------------------------------
For information on this and other Linux India mailing lists check out
http://lists.linux-india.org/
