printing to a remote IPP printer with lp is danghard

[Kurt Pfeifle]

> 1.  How was I supposed to go from the IPP URL
>
>         ipp://192.168.0.10/printers/HPLJ1012
>
>     to the above command?  It took me an hour to figure out (mostly
>     because I went down the blind alley of lpstat).  Why doesn't lp
>     simply take a URL as an option?  At least the documentation could
>     say how to construct an lp command line given an IPP URL.

Check your Debian bug report. I responded there even before here (but somehow my posting there took ages to show up), but didn't realize initially it was the same thing.

> 2.  I still can't check the print queue, query job status, or cancel a
>     job.  What is the right lpstat command line for this printer?

lpstat -h 192.168.0.10 -p             # all printers on 192.168.0.10
lpstat -h 192.168.0.10 -o             # all IDs of current jobs
lpstat -h 192.168.0.10 -p HPLJ1012    # printer HPLJ1012 at 192.168.0.10
lpstat -h 192.168.0.10 -l -p HPLJ1012 # "long" version info
lpstat -h 192.168.0.10 -o HPLJ1012    # current jobs queued for HPLJ1012

Once you know a job ID, you can run

  lprm -h 192.168.0.10 job-id

[...]
> But if my friend is running the CUPS server, I should only need the
> client commands, right?

Right.

But as you painfully experienced, this does not suffice if the CUPS server config is not set up correctly, or not set up in a way that makes printing *easy* for clients...

You run into one of various issues with Debian's self-willed decisions to configure CUPS defaults. See also Debian Bug #427559 for one more example....


--
Kurt Pfeifle
System & Network Printing Consultant --- Linux/Unix/Windows/Samba/CUPS
Infotec Deutschland GmbH - A RICOH Company ......... Stuttgart/Germany