Cups and lpd - eating jobs, printer stopped

[Anonymous]

Dear Johannes,
thanks for your quick reply.
I digged through the mentioned documents and couldn't find anything really solving my problems.
the lpd printing is fine, IF the printers stay online. But as they are most of the time offline/paper-out I'm in this trouble.

I digged again in the web and found two possible solutions
1. use direct port printing in jetdirect style URI: socket://pserver:9010; I'm actually testing it and it doesn't seem to timeout or disable the printer; but I'll have to see, how that config behaves in my customers daily usage
2. check this http://www.linuxprinting.org/beh.html; this cups-lpd behaviour on non-available printers seems to be known and this backend-error-handler seems to fix that.



>
> Of course if the LPD target does not respond it makes sense.
> Note that the LPD target is the LPD in the printserver box
> and not the printer itself.
> The sender (the CUPS lpd backend) does not talk to the printer,
> it talks to the LPD in the printserver box.
> Therefore for the the CUPS lpd backend it looks as if the
> "Remote host did not respond" (which it reports in error_log)
> which means that the printer is totally unaccessible and then
> the queue becomes disabled, see
> http://portal.suse.com/sdb/en/2004/05/jsmeix_print-cups-in-a-nutshell.html
> "The Backends"
>
> See our printing chapter in the Suse Linux 10.0 manual
> file:///usr/share/doc/manual/suselinux-manual_en/manual/sec.drucken.prob.html
> "Troubleshooting a Network Printer or Print Server Box"
> for a possible work-around for broken LPDs in printserver boxes.
>
>
> Kind Regards
> Johannes Meixner
> --