🚀 go-pugleaf

In article <HARTMANS.92Nov1152104@npc.ece.utexas.edu>, hartmans@npc.ece.utexas.edu (Sam Hartman) writes:
=	I've found printer communication to be useful. On the RS/6000,
=if it's configured right (big if), the print system will `write' a
=message back to a user indicating that their job has failed, including
=the printer output. However, for UNIX, I haven't seen any program that
=needed the two-way communication. We considered mounting a printer on
=token-ring, but even then, we were going to drive it with a server,
=and just use the ring for speed. (38400 gets slow!)

One can, of course, load an error handler which will produce a hard-copy of the
error message, and perhaps even a stack dump.  Of course, if the printers at
your site are either very busy or inaccessible to the users, figuring out which
error messages belong to which user could be problematic.

Also, don't forget that if you want to do accurate accounting for PostScript
printers, you've either got to run every job through a complete PostScript
parser or query the printer for the page count after every job.
--------------------------------------------------------------------------------
Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL

Disclaimer:  Hey, I understand VAXen and VMS.  That's what I get paid for.  My
understanding of astronomy is purely at the amateur level (or below).  So
unless what I'm saying is directly related to VAX/VMS, don't hold me or my
organization responsible for it.  If it IS related to VAX/VMS, you can try to
hold me responsible for it, but my organization had nothing to do with it.