lpq (CUPS client & LPRng server) queries show no jobs

[David Botsch]

See below...

On Thu, 09 Dec 2004 10:11:28 -0500, Michael Sweet wrote:

> David Botsch wrote:
>> ...
>> Question: Is this a bug? Is this the way it is supposed to work? Is
>> there some way to get the cups lpq/lprm/lpc clients to talk to the
>> LPRng print servers?
> 
> It is not a bug; there is no way for us to a) get the remote job ID and

There is not? Then how does the LPRng lpq do it? Briefly looking at
rfc1179, it looks like it's a simple client/server protocol where the
client sends the "Send queue state" command to the server, gets back a
response, maybe parses the reponse, and prints said response. I don't
think the client needs to actually keep track of the job number itself.

> b) wait for job completion via the LPD protocol which LPRng uses.  When
> printing via LPD, you lose job monitoring, control, and any guarantees
> of successful printing...
> 

I think you misunderstood what I meant. When you lprm a job, you aren't
lprm'ing it on the local machine, you are lprm'ing it on the remote
server. So, you look at the output of lpq, then lprm -Pprinter job_number
which causes lpq to send the "Remove jobs" command to the server which
does something then sends back a response.

So, I'm not entirely sure what you're getting at.

> IIRC, Patrick has an IPP module for Apache that works with LPRng which
> you could use to get the behavior you want - the jobs will stay in the
> local queue until completed by the server.
 
So, you are suggesting, cups on local computer to remote cups queue to
remote LPRng server? 

Thanks again.

-Dave B