Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site rtp47.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!harvard!talcott!panda!genrad!decvax!mcnc!rti-sel!rtp47!throopw
From: throopw@rtp47.UUCP (Wayne Throop)
Newsgroups: net.unix-wizards
Subject: Re: monitoring ttys
Message-ID: <97@rtp47.UUCP>
Date: Sun, 21-Jul-85 21:22:05 EDT
Article-I.D.: rtp47.97
Posted: Sun Jul 21 21:22:05 1985
Date-Received: Thu, 25-Jul-85 00:42:45 EDT
References: <1624@ecsvax.UUCP> <987@sdcsvax.UUCP>
Organization: Data General, RTP, NC
Lines: 18

> > Problem: Users frequently have problems with various application
> > programs, and in order to help them I have to go find them, look
> > over their shoulder while they reproduce the problem.

> I have added some code to our tty handler to do this.  It allows
> a tty to either share or take over the i/o to/from another tty.
>               Jeff Elman

The solution I have used is to use pseudo-terminals and a
session-logging program.  In other words, you have the user with the
problem log his terminal session to your terminal.  No kernel mods
necessary, and I beleive that there are terminal session logging
programs available for 4.2 BSD (the one I use is for another OS
entirely.)  You can't take over the user's terminal session with this
scheme, but it is available "off the shelf" so to speak, and serves most
of the needs.
-- 
Wayne Throop at Data General, RTP, NC
<the-known-world>!mcnc!rti-sel!rtp47!throopw