rainwatr@ucunix.SAN.UC.EDU (Don Rainwater) (11/16/89)
We're having problems with people printing non-text files to our printers. While the filtering that lpr does is fine for cases like 'lpr a.out', it does no checking for things like 'lpr file.dat' (where file.dat is not a text file) or 'cat a.out | lpr'. Is there something I can set in printcap (or elsewhere) so that the printer will not get (most) characters outside the printable range? I've tried 'nc=true' to eliminate control characters, but that didn't do much (any) good. Also, is there a way that I can eliminate the printing of the flag page? I tried sb=true, but that didn't work. In general, is there something I have to do to make a change to printcap effective besides making the change to printcap? The docs say that printcap settings are dynamic, but I'm not totally convinced. Thanks for any assistance. -- Don Rainwater, Univ. of Cincinnati Computer Center rainwatr@ucunix.san.uc.edu rainwatr@ucbeh.san.uc.edu rainwatr@ucbeh.bitnet
p554mve@mpirbn.UUCP (Michael van Elst) (11/17/89)
In article <61@ucunix.SAN.UC.EDU> rainwatr@ucunix.SAN.UC.EDU (Don Rainwater) writes: > > We're having problems with people printing non-text files to our >printers. I'm not very familiar with ultrix (I read this group because we got some DECstations). Nevertheless, it is generally possible to install a textfilter for automatic printing of dvi-files or to do accounting. This textfilter will get all characters printed and may filter out any non-printables. > Also, is there a way that I can eliminate the printing of the >flag page? I tried sb=true, but that didn't work. Try sh=true, it will suppress the printing of the (so-called) burst-page. > > In general, is there something I have to do to make a change to >printcap effective besides making the change to printcap? In our implementation (SunOS), you have to kill the lineprinter daemon (/usr/lib/lpd) and restart it again. Michael van Elst E-Mail: ..uunet!unido!fauern!immd!mlelstv ..uunet!unido!mpirbn!p554mve