Xref: utzoo comp.unix.questions:27299 comp.sys.sequent:770 comp.unix.admin:619
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!rpi!dali.cs.montana.edu!milton!uw-beaver!zephyr.ens.tek.com!tektronix!sequent!brians
From: brians@sequent.UUCP (Brian Sheets)
Newsgroups: comp.unix.questions,comp.sys.sequent,comp.unix.admin
Subject: Re: saving console i/o
Message-ID: <47654@sequent.UUCP>
Date: 1 Dec 90 06:26:32 GMT
References: <5c1eT1w163w@wvus.wciu.edu> <13140@vpk3.UUCP>
Reply-To: brians@crg1.UUCP (Brian Sheets)
Organization: Sequent Computer Systems
Lines: 16

In article <13140@vpk3.UUCP> craig@vpk3.ATT.COM (Craig Campbell) writes:
>In article <5c1eT1w163w@wvus.wciu.edu> pete@wvus.wciu.edu (Pete Gregory) writes:
>>We need to find a way to capture all /dev/console i/o for saving in a file,
>>while being transparent to anyone on that console.

If you have another *NIX machine you might try have the console output
hooked up to a tip line from another machine. The use that for the
console. The only problem in if the user does  a tilde . and
breaks the connection.


-- 
Brian Sheets KA7KDX                          "So, what if they went nowhere?"
5544 N Burrage.                              "Then this will be your big chance
Portland Or. 97217                            to 'get away from it all'"
503-578-4091                                                   -Star Trek II