On Mon, Jul 20, 2009 at 12:48:26PM +0530, Girish Kulkarni wrote: > Yes, CUPS not noticing jammed, busy or off printers is my basic > problem here too. It would be interesting to know what the CUPS > people have to say about this.
Afair there is a setting which allows you to change the behaviour, i. e. make cups do something, like disable the printer when it isn't ready. Unfortunately, I don't remember where and what that setting was. Perhaps you can find out more when you google for it. So you can print just fine until the remote printer isn't ready anymore? That you're not seeing any jobs in the queue would indicate that the job has either already been sent to the printer or has been aborted for some reason. If it has been aborted, it should show up in the log of completed jobs. If not, it's not impossible that the job has been transmitted to the printer correctly and that the printer swallowed it. Maybe the printer keeps a log of recent print jobs; their admin could check that and maybe find out what happened to your jobs. > I haven't tried LPRng. I preferred CUPS because it is Debian's > default and I want to keep things simple. But maybe I'll move to > LPRng at some point. Yeah, cups is easy to set up, but I don't know how well it works in a networking environment. The version I used was a pretty early version, and it has been improved a lot since, so they might have solved many problems. But lprng might be more reliable in your situation. Why don't you send the job to the print server they have that is using lprng instead of directly to the printer? That might work just fine and would be an easy solution. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
