Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!henry.jpl.nasa.gov!elroy.jpl.nasa.gov!cit-vax!csvax!mass
From: mass@hobiecat.caltech.edu (Mass Sivilotti)
Newsgroups: comp.sys.next
Subject: Printing DVI under 1.0 via lpd
Message-ID: <12810@cit-vax.Caltech.Edu>
Date: 28 Nov 89 19:52:20 GMT
Sender: news@cit-vax.Caltech.Edu
Distribution: comp.sys.next
Organization: California Institute of Technology
Lines: 23

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)