Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!rutgers!mailrus!husc6!rice!sun-spots-request
From: natinst!radian!cutter!markh@cs.utexas.edu (Mark Hebets)
Newsgroups: comp.sys.sun
Subject: Re: Dumb terminal screenlength problem
Message-ID: <528@cutter.UUCP>
Date: 12 Dec 88 00:13:13 GMT
References: <8811162313.AA08611@scuba.sunfun.eta.com>
Sender: usenet@rice.edu
Organization: Rice University, Houston, Texas
Lines: 32
Approved: Sun-Spots@rice.edu
Original-Date: 29 Nov 88 19:53:26 GMT
X-Sun-Spots-Digest: Volume 7, Issue 43, message 12 of 15

zeke@sunfun.eta.com (Robert K. Scott) writes:
> We have a curious problem with TELNET access to a SUN 3/280 running Sun/OS
> 3.2.    [Stuff deleted]  
>                                       The problem for these users is
> strange: sometimes their session thinks that they have more than 24 lines
> per screen, almost as if it thinks that they have a large Suntools window.

We see similar problems with both dialup and Telnet users once in a while.
I usually tell them to try two things:  First, if they're running Sun's
Telnet from PC-NFS, delete the file EM.SES from the NFS directory.  The
file saves some terminal setup info from session to session, and it may do
more harm than good if the last session had problems.

Second, put the following code in the user's .login file.  It checks to
see whether the login session inherited some terminal settings and clears
them.

# This code is from the Sun Software Technical Bulletin issue 1987-8
# It checks to see if a previous process left "rows" and "columns" set,
# and clears them.  

if( $TERM != "sun" ) then
	stty everything |& fgrep -s columns
	@ setscreensize != $status
	if($setscreensize) stty rows 0 columns 0
endif

-- 
   Mark Hebets, Software Applications Department, Radian Corp.
   PO 201088, Austin, TX  78720     (512)-454-4797
              sun!texsun!radian!markh
   cs.utexas.edu!natinst/