Mailinglist Archive: opensuse-features (893 mails)

< Previous Next >
[openFATE 303400] Allow to enable the backend error handler (beh) from the YaST printer module
  • From: fate_noreply@xxxxxxx
  • Date: Thu, 13 Aug 2009 16:47:11 +0200 (CEST)
  • Message-id: <feature-303400-16@xxxxxxxxxxxxxx>
Feature changed by: Maximilian Maher (maxmaher)
Feature #303400, revision 16
Title: Allow to enable the backend error handler (beh) from the YaST
printer module

openSUSE-11.1: Rejected by Stanislav Visnovsky (visnov)
reject date: 2008-07-08 09:39:42
reject reason: Postponing.
Priority
Requester: Desirable

openSUSE-11.2: Done
Priority
Requester: Desirable

Requested by: Lars Müller (lmuelle)

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.

Test Case:
- Test if you can enable the beh with Yast printer
+ - 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:
#1: Johannes Meixner (jsmeix) (2009-03-27 09:46:06)
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.



--
openSUSE Feature:
https://features.opensuse.org/303400

< Previous Next >
This Thread
References