I have CUPS 1.6.3.22 on Centos7 and when I print from AIX6.1 machine the job gets no name-title so it shows "Untitled" on the Jobs web page in the column "Name". And I want no banner page. I know that with the lpr command and a banner, the job title gets its correct value. I send the job via lp lp -c -d$PROFILES$.PRINTER -onobanner -n$PROFILES$.CONC_COPIES -t"$PROFILES$.TITLE" $PROFILES$.FILENAME The job comes in to my cups-server via cups-lpd I think. The log shows: D [05/Feb/2016:13:07:26 +0100] [Job 3507] argv="16_PRN" D [05/Feb/2016:13:07:26 +0100] [Job 3507] argv[1] ="3507" D [05/Feb/2016:13:07:26 +0100] [Job 3507] argv="root" D [05/Feb/2016:13:07:26 +0100] [Job 3507] argv="Untitled" D [05/Feb/2016:13:07:26 +0100] [Job 3507] argv="1" D [05/Feb/2016:13:07:26 +0100] [Job 3507] argv="document-name=ThisIsTest job-originating-host-name=myaix.machine.com job-uuid=urn:uuid:47ccd6c0-e2ff-3f0d-598e-466927f26e3b time-at-creation=1454674046 time-at-processing=1454674046" so as you can see the job-name(argv) is "Untitled" but in the options(argv) there we have "document-name=ThisIsTest" The question is: How to make Cups-LPD work like it is described in rfc2911 about IPP: https://www.rfc-editor.org/rfc/rfc2911#section-4.3.5 I mean that "...the printer SHOULD generate the value of the Job's 'job-name' attribute from ...the 'document-name' operation attribute"

I would like to take a $100 PCL-compatible laser printer and hook it to my home network either through Wi-Fi or by connecting it directly to a Linux server by USB. Instead of using the manufacturer-provided drivers, though, I want to be able to print PostScript documents directly. I imagine I will want to set up a print queue, GhostScript, and an IP address and port at which I can point other machines on the network. Also, I have a stack of CDs with PostScript fonts on them, and I would like to make these available to any machine that wants to print to the networked printer. I'm guessing this is done by copying the fonts somewhere where GhostScript can find them. Basically, I want to make the cheap printer look to other machines on the network like an old-school expensive PostScript-capable networked laser with lots of built-in fonts, like one of the high-end LaserWriters that Apple used to sell. In the old days with dot matrix printers and HP LaserJet printers that only had a parallel interface this sort of thing was common, but it seems like it's actually more obscure now that most printers are network-capable out of the box and are configured through a GUI. In particular I think I have an idea how I would have done the GhostScript setup with LPD by defining filters, but now all Linux distros seem to have CUPS installed out of the box.

I'm familiar with how to disable the banners on a system running xinetd (server_args = -o job-sheets=none in /etc/xinetd.d/cups-lpd). I've located the cups-lpd@.service file, which would appear to serve the same purpose, but the parameter names appear to be different, and I haven't been able to track down exactly how to pass the -o ... Is there any documentation for this? For now, I have run lpoptions -p $printer -o job-sheets=none for each printer, but this seems to be a sub-optimal approach.

I am debugging some printing issues on a small LAN, and although I'm fairly sure the issues I'm facing are not related to cups itself, I have been tinkering with the printing protocols that both CUPS and my printers (Konica Minolta Bizhub C224E and C3350) understand. That made me wonder: is it just a matter of knowing which protocols your printers support, or is there any hierarchy between them? From the extensive reading I did, I seem to be able to deduce that LPD is fairly old and IPP(14) the 'new kid on the block', but does this new protocol offer real benefits or not?

I have a linux (Fedora 22) machine and two thermal printers with a Digitus print server attached to each one. All are on the same LAN. Digitus print servers are each running LPD daemon and each one is configured to offer just one queue: lpd://192.168.1.2/queue and lpd://192.168.1.3/queue I just want to be able to lpr a file from Fedora to an LPD server using only an LPR client (No full CUPS install). I tried cups-client (dnf install cups-client), which installs lpr binary and I added the remote print servers to my /etc/printcap, but I get Bad file descriptor error whenever I run lpr. Any ideas?

In reference to: https://unix.stackexchange.com/questions/304559/redirect-lpd-lp-to-a-file/311484#311484 What about the scenario where you want to print and store the output in a file at the same time? I cannot seem to make this functionality work. I can get it to send to the printer, send to a text file, but I cannot get it to do both at the same time for each print job encountered. My simple of: file in /etc/printcap is: !/bin/sh Filter for HP Printing to do 10 pitch printing echo "\033E\033&l0o\033(8U\033(s0p10h12v0s0b3T\033&k3G\033&s0C\c" cat echo "\033E\c" cat I simply added to the cat command cat>>/usr/myname/store_the_text.txt. It will not do both. Thoughts?

We have an ancient Business Basic application which prints reports to a simple line printer, and we would like to capture that output to a file (to then scrape the data from it). This runs on Red Hat 8 (circa 2002). The Basic code OPENs then PRINTs to "LP", which makes its way to lpd printer lp. Inspecting a couple of random spool files that didn't get deleted in /var/spool/lpd/lp/, these look to have suitable content. So the question is, how to temporarily change something such that the Basic program sends its output only to a file (and that file doesn't get printed). One could achieve the effect by changing the Basic code, but the system is extensive, has many places where printing is performed, and there would be no easy way to offer an option at those places. Hence the pursuit of a way to do this, external to the Basic application, which can be instated and uninstated (to return printing to normal) from a script. In case it's relevant, the printcap entry: lp:\ :ml#0:\ :mx#0:\ :sd=/var/spool/lpd/lp:\ :af=/var/spool/lpd/lp/lp.acct:\ :sh:\ :rm=[ip address]:\ :rp=pr0:\ :lpd_bounce=true:\ :if=/usr/share/printconf/util/mf_wrapper: Thanks!

I have a USB printer, connected to a network print server (TL-PS310U). I want to print from Debian/Ubuntu to this printer. The queue is named 2409ee3c, but when I try to use lpr, it says that I need to add /version=1.1: user@user:~$ lpr -H 192.168.100.1 -P prt0 C0003022.che.spl lpr: Error - add '/version=1.1' to server name. Then I added the printer in CUPS (http://localhost:631) as lpd, with name Printserver: lpd://192.168.2.30/2409ee3c And I now can print with LPR: user@user:/run/shm$ export CUPS_SERVER=localhost:631; lpr -H 192.168.2.30 -P 2409ee3c C0003022.che.spl lpr: The printer or class does not exist. jsivil@jsivil:/run/shm$ export CUPS_SERVER=localhost:631; lpr -H 127.0.0.1 -P Printserver C0003022.che.spl My questions are: 1) Can I print with LPR directly to this printer behind a printserver? (I've tried netcat but it doesn't work for this printserver) 2) Does LPR need CUPS? Is it OK to use 127.0.0.1? 3) How can I avoid having to export the CUPS_SERVER variable prior to use lpr? Thanks

I have this *Epson L355* printer and according to www.openprinting.org I need to use the epson-201207w driver; however, on the CUPS config panel at http://localhost:631, the list of drivers only displays names like *Epson E 300*, *Epson EM 900C*, etc, but not *Epson L355* nor even *Epson L300* is present on the list. I tried to investigate the "human-readable" form name of the said epson-201207w driver but I can't find anything. Is there a way to know, or at least guess it?

I have a USB inkjet printer connected to a server running CentOS 5.7 (64). I installed and enabled cups-lpd so that another Unix server could send print jobs to that printer. The other Unix server assumes you want a banner page printed unless you use the -o nobanner option on it's lp command but I have an application there that uses lp but has no way to specify that option. Consequently, the [LPD](http://www.ietf.org/rfc/rfc1179.txt) transacion includes a "Print banner page" option (RFC1179 section 7.5) - at least I'm fairly sure (though I haven't checked with tcpdump etc) The result is I get an unwanted page saying "Cover Page" in big letters and giving Job-Id, Title and User name. This serves no purpose in my environment. **Is there any way to configure cups-lpd to ignore this "print banner page" flag?** ------------------ Update: Here's the start of /etc/cups/printers.conf # Printer configuration file for CUPS v1.3.7 # Written by cupsd on 2012-09-13 15:43 Info HP PSC 2210 Location Ground FLoor, Outlet A3/A4 DeviceURI usb://HP/PSC%202200%20Series?serial=XXXXXXXXXXXXXXX State Idle StateTime 1347547335 Accepting Yes Shared Yes JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy stop-printer

I need some recommendations on reasonable and up-to-date literature about network printing, the corresponding protocols (ipp, lpdp, ...), printjob authentication and accounting in heterogenous networks.

Hhow do I print duplex with Berkely lpr? (Other lpd suggestions are welcome) It has no options on simplex/duplex modes, but I guess, that they were somehow able to print duplex back then.

I am trying to print from SCO OpenServer remotely to a CUPS-LPD daemon running on a Red Hat Linux machine but it is dropping any print options from the print request. For example: lp -d remote-print-queue -o landscape print-file The options presented to the filter / backend only contains a job-uuid: argv="job-uuid=urn:uuid:96ba0666-ca3d-337b-69bf-81f70e9fa2a7" Is it possible to enable the pass-through of options using lpd remote printing?

To resume a job from command line I can call lpq which gives me the job number for example 211 and then lp -i 211 -H resume. However is there a way - to resume the *last* job without figuring out its job id first - to resume just all holded jobs with one command