[cups.general] When should a network backend retry?

[Michael R Sweet]

Ok, so the general rule is that a backend should retry all non-fatal  
errors. In the case of the standard CUPS network backends, we don't  
retry failed lookups or routing errors, but we *do* retry connection  
failures and other "busy" indicators. Thus, the error policy  
determines what happens for uncommon/unexpected problems that may  
require admin attention.


On Oct 29, 2009, at 10:48 AM, Tim Waugh <twaugh at redhat.com> wrote:

> If a network backend fails to connect to its network device because  
> the
> device is not currently present on the network, should it retry or  
> exit?
>
> The current CUPS backends retry in this situation.  However, the HPLIP
> 'hp' backend exits -- this is apparently in order to allow the printer
> error-policy to determine the behaviour.
>
> So is error-policy meant to cover connection failures where the device
> is not present on the network?  I haven't managed to find any  
> definitive
> documentation about this.
>
> Thanks,
> Tim.
> */
>
> _______________________________________________
> cups mailing list
> cups at easysw.com
> http://lists.easysw.com/mailman/listinfo/cups