Description of problem: If nscd is not running, then when /etc/resolv.conf changes, many applications (especially python applications) do not see the new nameserver changes. In bug #442172, the solution suggested was to make nscd non-optional, because this will properly fix this behavior. Other distros have patched glibc to stat /etc/resolv.conf regularly, but this is considered not acceptable for Fedora. If the solution is to make nscd non-optional, it should be done. Version-Release number of selected component (if applicable): nscd-2.11.1-1.x86_64
nscd must be optional, it also breaks many things when it is not. And those are more complex to fix than patching glibc to reload resolv.conf
Could you provide some details about what breaks? Especially given the comments in #442172.
For long using winbindd and nscd together has been known to have issues, like loops. Also nscd often has issues with DNS name caching as it assumes symmetric caching between A names and PTR numbers. There are very valid reasons why people disable nscd. I know about 442172, I had to track down and make Firefox add res_init() to solve krb auth problems. It's not pretty, but it is also not my problem if the glibc maintainer does not want to find a better solution, and tries to use this bug to push people to use nscd. There are many ways to solve this problem satisfactorily in glibc without having to use nscd.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.