Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!sri-unix!rutgers!mtune!codas!flmis06!mikel
From: mikel@flmis06.ATT.COM (Mikel Manitius)
Newsgroups: comp.unix.xenix,comp.sources.wanted,comp.unix.questions
Subject: Re: tty watcher
Message-ID: <198@flmis06.ATT.COM>
Date: Thu, 17-Sep-87 01:03:37 EDT
Article-I.D.: flmis06.198
Posted: Thu Sep 17 01:03:37 1987
Date-Received: Sat, 19-Sep-87 14:25:17 EDT
References: <1180@mtune.ATT.COM>
Organization: AT&T, Altamote Springs, FL
Lines: 14
Xref: mnetor comp.unix.xenix:761 comp.sources.wanted:2280 comp.unix.questions:4129

>2) is the major point here; there are no tty watchers that consist solely of a
>user-mode program that drops on top of a non-hacked UNIX system.

I saw this done on 4.1bsd once, I even had the code that did it. It was
a simple program that figured out where the clist struct was for that user's
tty driver, and scanned it repeatidly in /dev/kmem for changes. It would
output his input line by line.

This sort of thing should be feasable on most Unix systems... It's just
a pain figuring out where to find his clist, especially given just a
tty name.
-- 
				Mikel Manitius @ AT&T Network Operations
				mikel@codas.att.com.uucp | attmail!mikel