Xref: utzoo comp.sys.sgi:7404 comp.unix.internals:1554
Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!think.com!barmar
From: barmar@think.com (Barry Margolin)
Newsgroups: comp.sys.sgi,comp.unix.internals
Subject: Re: Where does TERM get set for Telnet logins.(Solution!)
Message-ID: <1990Dec18.074044.13043@Think.COM>
Date: 18 Dec 90 07:40:44 GMT
References: <1990Dec17.034330.27909@ccu1.aukuni.ac.nz> <1990Dec18.041334.7498@ccu1.aukuni.ac.nz>
Sender: news@Think.COM
Distribution: comp
Organization: Thinking Machines Corporation, Cambridge MA, USA
Lines: 17

In article <1990Dec18.041334.7498@ccu1.aukuni.ac.nz> russell@ccu1.aukuni.ac.nz (Russell J Fulton;ccc032u) writes:
>Dave was able to supply the crucial information that telnetd does not set
>TERM if negotiations with the client fail to produce a terminal type.
>From this I concluded that TERM must be already set for the telnetd process.

The 4.3bsd telnetd doesn't have this problem.  If it is unable to negotiate
the terminal type, it doesn't supply the "-p" (preserve environment) option
to /bin/login.  And when it does negotiate the terminal type, it sets the
environment that is inherited by /bin/login to only contain the TERM
variable.

I suggest you ask your vendor to adopt this strategy.
--
Barry Margolin, Thinking Machines Corp.

barmar@think.com
{uunet,harvard}!think!barmar