Please login or register to be able to edit or vote this feature.

Allow to enable the backend error handler (beh) from the YaST printer module

Feature state

openSUSE-11.1
Rejected Information
openSUSE-11.2
Done

Description

It should be possible to enable the backend error handler (beh) from the YaST printer module.

This is usefull if a network printer isn't always reachable.

Think of a printer switched on later than the startup of cups happens.

Testcase

  • first set up the queue as usual (i.e. without beh).
  • In case of backend errors and when additionally the default error handling is not what is wanted, one would first try if another CUPS error policy helps. One can change the CUPS error policy in YaST via "Policies".
  • If even another CUPS error policy does not do what is wanted, one could daisy-chain beh: Select the queue and "Edit" it. In the "Modify" dialog select "Connection Wizard" and therein "Daisy-Chain Backend Error Handler (beh)" usually leave the defaults for beh (or adapt them, read the help text in YaST), klick "OK" to go back to the "Modify" dialog. Now there is a new connection using "beh" available. Select this new connection in the "Modify" dialog and klick "OK" to apply the change to the queue.

Discussion


icons/user_comment.png J. M. wrote: (9 years ago)

I wonder why I am not included in such requests?

It is already implemented in the new yast printer module
for openSUSE 11.1 and accordingly also for SLE11
via the "Connection Wizard".

How to use it:

0.
Usually one would first set up the queue as usual
(i.e. without beh).

1.
In case of backend errors and when additionally the
default error handling is not what is wanted,
one would first try if another CUPS error policy helps.
One can change the CUPS error policy in YaST
via "Policies".

2.
If even another CUPS error policy does not do
what is wanted, one could daisy-chain beh:
Select the queue and "Edit" it.
In the "Modify" dialog select "Connection Wizard"
and therein "Daisy-Chain Backend Error Handler (beh)"
usually leave the defaults for beh (or adapt them, read
the help text in YaST), klick "OK" to go back to the
"Modify" dialog.
Now there is a new connection using "beh" available.
Select this new connection in the "Modify" dialog
and klick "OK" to apply the change to the queue.

icons/user_comment.png J. M. wrote: (8 years ago)

<pre>

Regarding the testcase:

You need to set up a queue where its backend intentionally must fail.

I suggest to set up a queue for a network printer

with an totally non-working host like

socket://nohost.nowhere:9100

where printing fails with "Unable to locate printer 'nohost.nowhere'"

and the queue will get disabled,

then you can change its URI to use beh to something like

beh:/0/0/30/socket://nohost.nowhere:9100

and re-enable printing and you will see

a continuously running backend "beh" and in

/var/log/cups/error_log

each 30 seconds a new message like

"E ... Unable to locate printer 'nohost.nowhere'!"

</pre>

Last change: 8 years ago
Voting
Score: 0
  • Negative: 0
  • Neutral: 0
  • Positive: 0
Feature Export
Application-xmlXML   Text-x-logPlaintext   PrinterPrint