Bug 461026
Summary: | cups-polld needs to call __res_init() on hostname failure | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Tim Waugh <twaugh> |
Component: | cups | Assignee: | Tim Waugh <twaugh> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 5.2 | CC: | ddumas, tburke |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-01-20 21:59:00 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tim Waugh
2008-09-03 14:57:44 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. To reproduce: 1. On machine A set up a print queue and mark it shared. Set 'Publish shared printers connected to this system' so that it is accessible on the network. 2. On machine B, use the firewall to *block* UDP port 631. Configure CUPS to poll from machine A instead, like this: cupsctl BrowsePoll=machine-a.mynetwork 3. Now on machine B stop CUPS, 'rm /var/cache/cups/remote.cache', and bring down the network interface. 4. Start CUPS on machine B and verify that lpstat -s shows no printers (there is no network connection to do that with). 5. Now bring up the network interface and wait a few minutes, then run 'lpstat -s'. This should show the remote queue, but the failing package will not because even though the network connection is up, it cannot resolve the hostname due to the resolver cache remembering that there is no connection. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-0201.html |