Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!agate!garnet.berkeley.edu!dean2
From: dean2@garnet.berkeley.edu (Dean Pentcheff)
Newsgroups: comp.sys.next
Subject: Printing daemon hanging in 2.0?
Summary: lpd seems to go to lunch occasionally.
Message-ID: <1991Jun12.024405.24440@agate.berkeley.edu>
Date: 12 Jun 91 02:44:05 GMT
Sender: Dean Pentcheff
Reply-To: dean2@garnet.berkeley.edu (Dean Pentcheff)
Followup-To: comp.sys.next
Organization: Department of Integrative Biology, UC Berkeley
Lines: 21

We've recently upgraded our 68030 cube to the 2.0 OS and printing has
become a bit flakey.  Most of our printing is via PC/NFS (which uses
the standard lpr system) to the NeXT's printer and to two serial-
attached printers.

Since the upgrade we've had intermittent printing failures.  For no
apparent reason printing ceases (sometimes in mid-job), lpq tells us
that daemons are not present (and ps confirms that) and we're stuck.
Ps shows a single /usr/lib/lpd still present.  Starting another does
nothing.  However, killing the old /usr/lib/lpd (so that now there are
no lpd daemons present) _then_ starting a new one makes everything
peachy-keen again.

Is this a known bug?  Any ideas?

Thanks!

-Dean
-- 
Dean Pentcheff  (dean2@garnet.berkeley.edu)
Department of Integrative Biology, University of California, Berkeley CA 94720