[cups.general] Problems with LPD inbound jobs

[Wes Hardin]

On 02/22/2012 11:41 AM, Paul Conklin wrote:
> so I have paul (socket queue to actual printer) and paul2 (lpd queue pointing
> to paul)
> 
> so if i print to paul2, it should make it to paul by way of lpd and to the
> printer.  I've tried using lpd to connect to paul from both AIX and Windows,
> and i can connect, but it errors out.  Looking through the logs it appears
> that it connects, sends data, and the mini-server doesn't respond (or
> responds incorrectly)  that's why I set up paul2 to simulate the same thing,
> but rules out networking and everything else.
> 
> Make sense?

No, it doesn't.

cups-lpd is the frontend that accepts LPD jobs and does the "translation" to CUPS.

Setting up a queue with lpd:// is using the LPD backend, how CUPS talks to the
printer (or other LPD print server).  This is how you move data out of CUPS.
You can't set up a queue using the LPD backend and suddenly start accepting jobs
from legacy LPD clients.

To accept jobs from LPD clients, you need to configure cups-lpd.  You don't
(typically) setup queues for the same printer based on the incoming protocol.

You should delete your "paul2" queue.

/* Wes Hardin */