Redhat print queue type which more better?

denghazali11 · 05-08-2019, 10:20 PM

i want to ask any one who experiences with redhat print queue, which type print queue is more better to use generic post script or local raw print queue? then how can we check the print queue already exists used what type of print queue. is there any configuration file can we refer.

ferrari · 05-09-2019, 03:52 AM

Welcome to LinuxQuesions.org. From reading your post, I'm not sure about what level of understanding you have about CUPS queues and *nix drivers. PostScript is a "device independent" page description language used by a lot of high-end printers, and was the native print job format prior to CUPS version 1.5 IIRC. A raw print queue would normally only be used to send print data from a CUPS client to a remote CUPS server, or for software that might talk directly with a specialised printer. So, completely different things. CUPS "device dependent" drivers are used to take a print job eg CUPS PDF file and process it via a filter chain into a format that the user's printer can understand (which may be a proprietary protocol).

Useful references:
https://en.wikipedia.org/wiki/CUPS
https://en.opensuse.org/Concepts_printing

ferrari · 05-09-2019, 03:56 AM

Print queues explained (from the openSUSE wiki page)...

Quote:

For each print queue there is a PPD file which CUPS provides to application programs so that the printer-specific options are available in the printing dialogs.

In particular for non-PostScript printers CUPS runs the printer driver and sends its result to the printer device. To do this, CUPS must know which printer driver belongs to the printer device and how the printer device is connected to the computer so that CUPS can send printing data to the printer device.

Therefore "set up a printer" means to "set up a print queue" and tell CUPS for the particular queue:

How the printer device is connected to the computer
Which printer driver belongs to the printer device (via the PPD file)

To see what is already set up on a given host, the lpstat command can be useful

Code:

lpstat -t

and check the associated PPD file(s) in the /etc/cups/ppd/directory.