[cups] Cups / CentOS-6

[Joseph Henley]

Michael,

The reason you listed is why I'm trying to use IPP.  That plus the fact 
that a VERY similar machine continues to run fine with IPP on the 
printer.  And in fact, the problem printer used to work fine as well 
using IPP.  And FWIW, I have tried using the socket and got identical 
results.

I suspect the problem lies somewhere in the set up of the queue.  I have 
compared the set up between the working machine and the non-working 
machine but can find no differences.  That includes double checking 
commonality in sym-links, general libraries (glib, etc), config files, 
etc.  No joy.

I have removed cups; did a search and destroy on any left over 
sym-links, config files, etc.; and then re-installed cups.  Still no joy.

I am seriously stuck.  As always, help and suggestions are welcome.

Joe Henley
On 10/09/2015 08:10 AM, Michael Sweet wrote:
> Douglas,
>
>> On Oct 9, 2015, at 2:21 AM, Douglas Kosovic <doug at uq.edu.au> wrote:
>> ...
>> You mention you are using IPP to connect to the printers. Due to issues with printer implementations of IPP, it is generally recommended to use port 9100 socket connection instead with CUPS.
> Generally speaking, any printer made in the last 5 years (certainly any printer advertising AirPrint support) has excellent IPP support.  That's one of the reasons we are advancing IPP/1.1 and 2.0 to full standard status (demonstrated interoperability and widespread implementation...)
>
> That said, if this queue is using a vendor driver, it *may* work better with socket if the driver needs to interrogate the printer over the data channel - IPP is unidirectional for print data while socket is bidirectional.
>
> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>
> _______________________________________________
> cups mailing list
> cups at cups.org
> https://www.cups.org/mailman/listinfo/cups
>