<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Oct 30, 2009, at 2:23 AM, Johannes Meixner wrote:</div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000">...</font></div></blockquote><blockquote type="cite"><div>Are failed lookups or routing errors really fatal errors<br>in any case nowadays?</div></blockquote><div><br></div></div><div>A failed regular hostname lookup (<a href="http://printer.example.com">printer.example.com</a>) means that your dedicated DNS services are either not responding or the hostname has gone away. There may be some changes for us to make in this arena, e.g. failure to contact the DNS server should be a retry instead of "stop this printer", but if the hostname is no longer defined there is no possible recovery without the admin fixing the DNS or printer configuration (which require the backend process to be re-run to pick up the changes...) In any case, we'll need a bug on <a href="http://cups.org">cups.org</a> to track any change to the CUPS code... :)</div><div><br></div><div>If you use a dynamic host or service name (for CUPS that means a .local hostname or a service name that we resolve at print time), we retry the lookup until it succeeds since those names are intended to be used in dynamically changing networks.</div><div><br></div><div>Failed routing is tricky; we already retry for EHOSTDOWN and EHOSTUNREACH, but not for ENETDOWN or ENETUNREACH... I've not seen any bugs on <a href="http://cups.org">cups.org</a> on this being a problem, though...</div><div><br></div><div>___________________________________________________</div><div><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div>Michael Sweet, Senior Printing System Engineer</div><div><br></div></span><br class="Apple-interchange-newline">
</div>
<br></body></html>