Path: utzoo!attcan!uunet!husc6!rice!sun-spots-request
From: rcd@fed.frb.gov (Bob Drzyzgula)
Newsgroups: comp.sys.sun
Subject: Re: Dumb terminal screenlength problem
Message-ID: <344@arcfs1.fed.FRB.GOV>
Date: 22 Dec 88 03:53:14 GMT
References: <8811162313.AA08611@scuba.sunfun.eta.com> <2043@vu-vlsi.Villanova.EDU>
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 21
Approved: Sun-Spots@rice.edu
Original-Date: 15 Dec 88 14:24:51 GMT
X-Sun-Spots-Digest: Volume 7, Issue 71, message 1 of 16

This problem has vexed me for over a year, and I may have finally found
one actual reason for its occurance. It goes something like this: User A
rlogins from suntools to some server machine, runs some stuff, and exits
without cleaning up completely. Process remains running on server with
user A's pseudo-tty as controlling terminal. User B telnets to server from
terminal server, gets same pseudo-tty. Unix now thinks that that old
process belongs to new session. Even will dump output from command to user
B's terminal. What's more **Unix thinks that the new terminal has the old
session's terminal characteristics**. Finding the offending process,
killing it off, logging out and back in again makes the problem go away.

Up until last week, when I discovered this, I always had to reboot the
machine to make the problem go away. I have seen this work twice since.
Don't know if other things cause this that hence cannot be fixed in this
way. Boggles the mind.

-Bob

Bob Drzyzgula
Federal Reserve Board, Washington, DC, 20551
uucp: uunet!fed!rcd; Internet: rcd@fed.frb.gov