Errors sending large numbersofdocuments toprinter

[John Lussmyer]

The delay seems to have worked.  The big Sunday night print run all worked with none of the errors reported.
One of the printers was even off-line and properly spooled up all 389 jobs for it.


> On Mar 4, 2010, at 12:46 PM, John Lussmyer wrote:
> > Michael Sweet wrote:
> >>=20
> >> Let me know how that works out - you could be running into a file =3D
> >> descriptor limit (too many open files) that can yield failed jobs =3D
> >> without the usual logging.
> >>=20
> >=20
> > Adding delays isn't what I would call a good solution though.
>
> But it will help us determine what (and where) the problem is - right =
> now you have a symptom but not the cause...
>
> > It still won't handle the case of the printer just being out of paper =
> for 12 hours.
> > Does CUPS have special handling for printers that have their own spool =
> space, and happily spool jobs internally?  One of the printers we are =
> having this problem with has a big HD and spools jobs to it.
> > We are wondering if the CUPS/Printer communications handles the case =
> when the printers internal spool space fills.
>
>
> CUPS normally only spools one job at a time to a printer.  As for a =
> printer running out of its own spool space, we depend on the printer to =
> report that error back, which only works for LPD or IPP (and better with =
> IPP since it can actually report what the error is rather than just =
> success/fail...)
>
> ________________________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>
>
>
>