Feature changed by: Maximilian Maher (maxmaher) Feature #303400, revision 18 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: - - 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 + * 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. #2: Johannes Meixner (jsmeix) (2009-08-13 17:10:26) <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> -- openSUSE Feature: https://features.opensuse.org/303400