Overhauled CUPS: Improved Unix Printing - page 4
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.
Solid state disks (SSDs) made a splash in consumer technology, and now the technology has its eyes on the enterprise storage market. Download this eBook to see what SSDs can do for your infrastructure and review the pros and cons of this potentially game-changing storage technology.
- 1Linux Top 3: Alienware, KDE and Ubuntu 13.04
- 2Linux Top 3: Linux Mint Olivia, Fedora 19's Cat and Ubuntu's Mission Accomplished Moment
- 3GNOME 3.8 Debuts New Open Source Linux Desktop
- 4Linux Top 3: Linux 3.10 Goes Long, Linux 3.11 Advances as LXDE Merges
- 5Linux Top 3: Ubuntu Kaylin, Debian Wheezy and Linux Mint