Path: utzoo!mnetor!tmsoft!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!yale!eagle.wesleyan.edu!hdtodd
From: hdtodd@eagle.wesleyan.edu
Newsgroups: comp.sys.apollo
Subject: lpr/lpd problems (revisited)
Message-ID: <1991Mar3.135954.39621@eagle.wesleyan.edu>
Date: 3 Mar 91 18:59:54 GMT
Organization: Wesleyan University
Lines: 31


	I am running SR10.2 on 2500/3500's with BSD 4.3 as the primary working
environment.

	I have followed the discussion of lpr problems with interest,
since I have the infamous "cannot start daemon" problem.  I followed the
very helpful suggestions of Kniveton about lp? protections and ownership,
Peterson about /usr/spool/lpd protections and ownership, Peyerl about
/usr/spool/lpd/servername and about /dev/printer, O'Brennan and others
about having llbd running.

	Despite all the helpful advice I still have a very curious
problem.  If I queue something, lpr/lpd reports that it cannot start the
daemon (yes, the master lpd is running).  An "lpc restart all" does
nothing but report that it can't start the daemon, either.  HOWEVER ... if
I kill the /usr/lib/lpd  master process and restart with /usr/lib/lpd &,
the job gets printed (!).  The lpd process stays alive, but it can't seem
to spawn subsequent daemons to handle new requests.

	Attempts to log errors with syslogd have been unsuccessful: I
asked for almost all levels of lpr errors to be logged with no success.

	I have verified that /usr/spool/lpd/servername matches hostname,
I've check the protections of the directories and lp? programs, and I've
verified that there is a /dev/printer and a /dev/sio1.

	Can anyone suggest anything else I can check.  Thanks for any
advice.

						David Todd
						Wesleyan University