April 19, 2019

Overhauled CUPS: Improved Unix Printing - page 4

Web Interface

  • July 20, 2006
  • By Carla Schroder

CUPS still offers no way to determine if a printer is actually connected, powered on, and ready to print before you send a print job to it. It would be nice to know in advance, instead of waiting for the "Printer not connected; will retry in 30 seconds..." message.

There is confusion over remote and local printers. When you first open the CUPS interface, the URL is http://localhost:631/. Then when you click on a remote printer, you're in the remote CUPS interface, with a remote URL like http://uberpc.alrac.net:631/printers/canon-pixma4200. This can get confusing when you have administration privileges on the local PC but not the remote machine, and you find yourself staring at a 403 error.

Print queues are far too persistent. Few experiences match the joy of having a big print job disappear mysteriously into the ether, only to have it pop out a week later when you don't need it anymore, and everyone is in a hurry. I would like to have print servers empty their queues at configurable intervals. For a small shop with just a few users, hourly would work nicely. For a bigger office with a lot of printing, maybe nightly at midnight. Or maybe hourly, given how wasteful some people are who send reams of pages to the printer, then never pick them up. (You know who you are--shame! Think before you click!) No big deal if the wastrels lose a few print jobs.

Most Popular LinuxPlanet Stories