Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!mcnc!ecsvax!dukeac!klg
From: klg@dukeac.UUCP (Kim Greer)
Newsgroups: comp.unix.wizards
Subject: Re: lpr output filters
Message-ID: <1347@dukeac.UUCP>
Date: 13 Apr 89 12:27:54 GMT
References: <1158@novavax.UUCP> <8414@xanth.cs.odu.edu> <16878@mimsy.UUCP>
Reply-To: klg@dukeac.UUCP (Kim Greer)
Distribution: usa
Organization: Academic Computing, Duke University, Durham, NC
Lines: 23

In article <16878@mimsy.UUCP> chris@mimsy.UUCP (Chris Torek) writes:
++The discussion is really about `files that can be viewed on a terminal
++but not printed'.
++
++It is worth noting that this effort is doomed to failure, as there
++are terminals that are printers, or have integral printers.
++
++If you have physically secure terminals, you could set something up
++so that the files can be viewed only on /dev/ttyA2, /dev/ttyh0, and
++so forth.
++-- 
++In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
++Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris

  I think Chris is right; it is doomed.  Even "secure" terminals can
run "script"  to capture the screen output and then immediately print
the typescript file.  You don't have script on your system?  A pd
version is available.
-- 
Kim L. Greer                       
Duke University Medical Center		try: klg@orion.mc.duke.edu
Div. Nuclear Medicine  POB 3949            dukeac!klg@ecsgate
Durham, NC 27710  919-681-2711x223      ...!mcnc!ecsgate!dukeac!klg           		fax: 919-681-5636