[cups.general] Cups and lpd - eating jobs, printer stopped

[Johannes Meixner]

Hello,

On Feb 15 10:39 motionseverywhere at gmx.net wrote (shortened):
> tested with Suse 9.2/cups 1.1.21 and Suse10 Prof/cups 1.1.23:
> cups configured to print to external printserver (different
> brands tested like sercom, planet, intel)
> Printer itself are most of the time off-line/out of paper,
> when the print jobs are started
.... 
> So it looks cups is unable to handle lpd targets, which are offline.

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
-- 
SUSE LINUX Products GmbH, Maxfeldstrasse 5      Mail: jsmeix at suse.de
90409 Nuernberg, Germany                    WWW: http://www.suse.de/