Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!munnari.oz.au!bruce!merlin!robinb
From: robinb@bhpmrl.oz.au (Robin Brown)
Newsgroups: comp.sys.apollo
Subject: Re: problems with getting printing working
Message-ID: <1991Jan8.052400.23579@bhpmrl.oz.au>
Date: 8 Jan 91 05:24:00 GMT
References: <1991Jan5.044703.12219@eng.umd.edu>
Sender: usenet@bhpmrl.oz.au (USEnet nntp account)
Organization: BHP Melbourne Research Laboratories, AUSTRALIA
Lines: 33

skum@eng.umd.edu (Allon Stern) writes:

>Configuration: a DN3000 running SR10.3 with max Aegis/BSD4.3 installed

>Problem: lpd will not start up.

>What happens when /usr/lib/lpd is started is that it creates two
>lpd processes, then one of them dies.  The other one sticks around.
>The one that dies, I believe, is the one that is supposed to be
>controlling the printer.
That's what is supposed to happen.  When lpd is started is spawns a copy
of itself for each entry in your printcap file.  These check to see if
any jobs are outstanding, process them and then die. The parent lpd
process sits and listens of print requests and spawns copies of itself
to process any that it receives.

># lpc
>lpc> restart all
>cx:
>        no daemon to abort
>cx:
>        couldn't start daemon
>lpc> status
>cx:
>        queuing is enabled
>        printing is enabled
>        no entries
>        no daemon present
This is normal, a daemon will not be present unless a job is being processed.
Your printcap file looks reasonable but then never having set one up like 
that I can't be sure.  More details on exactly what happens might help.

Robin