Xref: utzoo comp.unix.questions:27533 comp.unix.programmer:676
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!wciu!wvus!pete
From: pete@wvus.wciu.edu (Pete Gregory)
Newsgroups: comp.unix.questions,comp.unix.programmer
Subject: print spooler
Message-ID: <1213T2w163w@wvus.wciu.edu>
Date: 12 Dec 90 19:52:23 GMT
Organization: World Vision U.S.
Lines: 31

Hi, netters...

We want to replace, for a specific application, our print spooler.  Our
application, with 60 operators on data entry screens (Informix 4GL), writes
a three-line audit record to the printer (no form feeds, just continuous
output, and yes, it MUST go to the printer) via the print spooler.

The print spooler introduces way too much overhead, and we'd like to
circumvent it by somehow writing directly to the device.

I've tried writing directly to the printer (cat file >> /dev/ttyxx), but
tests indicate that records can get scrambled - two records hitting at the
same time can get mixed up.

I thought about piping the audit record to a C program that writes to
a message queue, and have a daemon read the message queue and write to the
printer directly.

BTW, this is a Unisys 6000/70 (Sequent S27) running Dynix, with AT&T and UCB
spooler packages available.  We're using the AT&T spooler now, and we'll 
continue to for "regular" print files.

Certainly someone else has been in this situation, and has solved it.  I'd
as soon not reinvent the wheel.
 
Pete Gregory, UNIX SA  |  pete@wvus.wciu.edu                  |
World Vision USA/ISD   |  wciu!wvus!pete                   ___|___
919 W. Huntingon Dr.   |  Voice: 818/357-7979 x3347           |
Monrovia, CA  91016    |  FAX:   818/303-6212                 |
                                                              |
Romanian orphans need our help!  Call 1-800-777-1229