NetNews Usenet Archive 1992 #26/NN_1992_26.iso/spool/comp/sys/sgi/16353

Text File | 1992-11-12 | 1.8 KB | 43 lines

Newsgroups: comp.sys.sgi
Path: sparky!uunet!utcsri!skule.ecf!torn!spartan.ac.BrockU.CA!edik
From: [e-mail] (Ed Sternin)
Subject: Telnet bug? or feature?
Message-ID: <[e-mail]>
Organization: Brock University, St. Catharines Ontario
X-Newsreader: Tin 1.1 PL4
Date: Thu, 12 Nov 1992 21:19:50 GMT
Lines: 32

I thought I was being clever: at login, in one of the
scripts (.cshrc, I guess) I check if DISPLAY is defined,
I check if remotehost is defined, and set things appropriately.
The problem is that if all that fails, I say aha, we must be local,
so
  setenv  DISPLAY :0
or something like that.  Having done that, I rlogin to another
machine, and rlogin upon seeing :0 prepends a proper fully qualified
name, so that on the new machine I have DISPLAY=old.machine.full.name:0,
and all windows work fine.  Now I telnet to the same machine; telnet
sees :0 and prepends a local name, too -- BUT ONLY THE NICKNAME, not
the fully qualified domain name!!  So on the new machine I end up with
DISPLAY=old:0  to use the same example.  This only has meaning if I moved
within a subdomain, but fails miserably when I hop across subdomains.

If in telnet> I listenv (or is it printenv?) I can see the error even before
OPENing a connection, as what telnet will send out as the local DISPLAY
name.

Any fix?   Any easy shell way of obtaining a fully qualified domain name
of my local machine -- so that I could always set DISPLAY to
  old.machine.full.name:0     and not just
  :0
???

Thanks for your help.

--

-------------------------------------------------------------------------------
Ed Sternin, Dept. of Physics, Brock University, St.Catharines, Ontario, L2S 3A1
  voice: [phone] ext.3414   FAX: [phone]   email: [e-mail]