Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make handling of backend errors more configurable #1764

Closed
michaelrsweet opened this Issue Jun 9, 2006 · 5 comments

Comments

Projects
None yet
1 participant
@michaelrsweet
Copy link
Collaborator

michaelrsweet commented Jun 9, 2006

Version: -feature
CUPS.org User: till.kamppeter

On the cups.general mailing list/newsgroup was some discussion whether with CUPS 1.2.x the wrapper backend "beh" (Backend Error Handler, http://www.linuxprinting.org/beh.html) still makes sense. See the thread

Is http://www.linuxprinting.org/beh.html still useful with cups 1.2.X?

in the archives on

http://www.cups.org/newsgroups.php

Go to

http://www.cups.org/newsgroups.php?gcups.general

and enter

http://www.linuxprinting.org/beh.html

as search term to see the whole thread.

beh was developed in CUPS 1.1.x times, where an error condition in a backend (for example printer out of paper) disabled the queue and required someone with root privileges (or in admin group depending on CUPS config) had to re-enable it. beh has made this behaviour configurable, so that one could also repeat or discard a failed job and keeping the queue enabled.

Now CUPS 1.2.x offers configurability of the handling of backend errors, too, but with less possible settings than beh.

My suggestion is to add the following features in future versions of CUPS:

  • Make nfinite retries possible
  • give also possibility to disable the queue after the given retries
    are done without success
  • Retry interval and number of retries configurable per printer
  • All this configurable in the web interface
@michaelrsweet

This comment has been minimized.

Copy link
Collaborator Author

michaelrsweet commented Sep 24, 2007

CUPS.org User: PetrusR

Hi,

I like the idea of being able to retry printing a job when there is a problem instead of stopping the print queue or stopping the job, but the current way how CUPS works causes printouts to get out of sequence, when I set the error policy of the printer to retry.
It is absolutely crutial for us to be able to print jobs in the sequence it was submitted to CUPS.

The only way currently for me to ensure the sequence is to set the error policy to stop the printer when there is a problem.
This requires a lot of baby sitting of the queues as we don't control the users and their printers.

@michaelrsweet

This comment has been minimized.

Copy link
Collaborator Author

michaelrsweet commented Oct 24, 2007

CUPS.org User: alna2007

I am working in a company where we need to print invoices in order. I agree with the above, it is crucial for us to be able to have the invoices printed in the sequence they were given. Have the option of retrying a given number of times before stopping the job would be a really great feature.

@michaelrsweet

This comment has been minimized.

Copy link
Collaborator Author

michaelrsweet commented May 17, 2008

CUPS.org User: PetrusR

Hi Till,

You probably saw my other STR 2555 post, about this.
Basically we now use BEH for all our printers in CUPS to retry jobs, while preserving the sequence.
This is the only way thus far found that can do this.

I do see a need for BEH, until it or equivalent features are implemented in CUPS or it's backends.

The only problem thus far found with BEH is that if I stop a printer while it was trying to submit a job to the printer, it's child lpd process does not get killed when it is killed by CUPS.
Instead the child goes to init as the parent and I have to kill it manually in Unix.

@michaelrsweet

This comment has been minimized.

Copy link
Collaborator Author

michaelrsweet commented May 21, 2008

CUPS.org User: rboss

hi Petrus,

i addressed the problem of killing also subprocesses in RFE
STR #2829
also providing a patch to change the behaviour

@michaelrsweet

This comment has been minimized.

Copy link
Collaborator Author

michaelrsweet commented Mar 31, 2014

CUPS.org User: mike

This has been "fixed" since 1.3 I think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.