Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!CC3.CC.UMR.EDU!obrennan
From: obrennan@CC3.CC.UMR.EDU (obrennan)
Newsgroups: comp.sys.apollo
Subject: RE: LPD/LLBD
Message-ID: <9102211448.AA00841@cc4.cc.umr.edu>
Date: 21 Feb 91 14:48:23 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 32


		obrennan@CC3.CC.UMR.EDU (obrennan) writes:
		>	Although lpd starts up fine, the jobs just get queued up
		>	and don't move.  An "lpq -Pxx" gives "Warning: no daemon present"
		>	and an "lpc restart xx" gives "no daemon to abort, starting daemon"
		>	But the daemon is there....
		>	
		>Do you have LLBD running?                             
		
		I don't see what llbd has to do with it.  Unix lpd stuff isn't
		NCS based as far I as I'm aware. 
		
	-------------------------------------------------------------------------------------------
	"Managing BSD System Software A00" states on page 6-3:
	
	    On Domain/OS, communication between a client (lpr, lpc, etc.) and the server (lpd) is
	    accomplished by using the Network Computing System (NCS). As a result, a local location
	    broker (/etc/llbd) must be running on the node providing the line printer daemon....
	
	Although I haven't checked to see if the above is a true requirement, I feel safer having
	done what was suggested (then my bases are covered when I report problems). I'm fighting
	with some LPD troubles myself. If I learn anything new, I'll try to post it to the net.
	
	
	Gerry O'Brennan
	Programmer/Analyst II
	Computing Services
	University of Missouri - Rolla
	------------------------------
	obrennan@apollo.cc.umr.edu
	c0022@umrvmb.umr.edu          
	------------------------------


Brought to you by Super Global Mega Corp .com