Subject: Re: papd problem
From: Bill Holyoak (bill@powergateway.com)
Date: Sat Oct 28 2000 - 13:58:00 EDT
<snip>
> 1. The printer name starts on the first character of the line. No
> leading
> spaces or tabs.
>
> 2. All the other lines must be tabbed in with one tab character. Spaces
> won't work.
>
> 3. If you use line continuation, make sure you don't have a space after
> the \, such as ":\ ". The \ must be the last character on the line.
>
> Otherwise, your papd.conf above looks good.
You were right. My papd.conf file was not formatted like you outlined it should
be. I restarted papd and I can do a papstatus -p lp and it works. However, the
message that it gives back is still "status: print spooler processing job". I
checked my /var/log/messages file and found that there HAD previously been
problems starting papd (even though papd showed up with a 'ps aux'). Now it
starts without error, so I know it's running right.
Could this be a permission's issue? I know that papd somehow interacts with
LDP, but I don't have a whole lot of experience with both. When I type lpq, it
gives me:
#lpq
Printer: lp@cyborg
Queue: no printable jobs in queue
Status: server finished at 02:33:28
while papstatus tells me the queue is busy. Where does papd try to put the
print job (where is the actual physical location of the 'queue')?
If anybody could give me any ideas at all... I think I'm almost there!
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:32:30 EST