Comment 5 for bug 458999

It seems you confuse an internal retry of the backend
while it tries to establish the communication
with its recepient with an overall retry of the whole print job
by the cupsd.

Why do those users think a long running (a wek is really not "forever")
loop of retries with reasonable sleeps in between is bad?

If you like to please all your users, make those settings adjustable
via optional additional parameters to your device URI.

For more info what I think about the whole issue have a look at
https://bugzilla.novell.com/show_bug.cgi?id=337794#c16
in particular:
----------------------------------------------------------
As long as the backend cannot establish a communication with its
recipient, it cannot cause damage when it loops infinitely and
retries again and again (with a reasonable sleep time between
each retry).

In contrast if a working communication with its recipient crashes,
it should not re-try the same job (which means print it again from
the beginning).
But the backend can also not simply wait in an infinite loop until
it can re-establish the communication and then send the rest of
the job because usually this doesn't continue the job where it was
interrupted (which happens usually somewhere within a page but the
backend doesn't know about pages - it just sends a stream of bytes).

The more I think about it, the less I like the idea to "solve" it
via another single default CUPS ErrorPolicy.
----------------------------------------------------------