mass@hobiecat.caltech.edu (Mass Sivilotti) (11/29/89)
Upon our recent upgrade to 1.0, our Cube's ability to print DVI files has somehow broken. Reading the new docs, it appears the legit approach is to "dvips <file>.dvi"; this pipes to lpr, and WORKS OK. The problem arises if one attempts the (similarly documented) approach: "lpr -d <file>.dvi". In this case, the lpd daemon commits suicide and the print queue is blocked forever. We have a heterogeneous network of machines, and the need for "lpr -d" is acute (i.e. not everyone has logins on the NeXT, but we would still like it to be available as a print server...). Under 0.9, lpd ran a shell script "psint.sh" that processed the various kinds of print jobs (PS, CAT, etc.). Although the script (or its equivalent) still exists in /usr/lib/transcript, I can find no evidence that it is being called/used. Any suggestions are welcome. If this is a trivial problem resulting from my stupidity, please reply by email. Thanx in advance, mass sivilotti (mass@csvax.caltech.edu)
mass@garfield.caltech.edu (Mass Sivilotti) (11/29/89)
If the /etc/printcap file does not contain an entry for the appropriate filter, it appears that lpd dies, leaving the offending file in the print queue (thereby jamming up the queue). Fixing that, and remembering that NetInfo is always in the way, made the printer work. Thanks to all those who responded (will respond?!?) to my plea for help! mass